Check the server log to see what happens there.
It might be some misspelling when the bean tries to look up something in JNDI.
Maybe, looking up java/comp (with no ':' ), instead of java:/comp.
Thanks for the reply.
The first time the client is run the server log shows the following:
2002-07-30 12:40:43,646 DEBUG [org.jboss.ejb.plugins.LRUEnterpriseContextCachePolicy] Resized cache for bean live_CU01_1: old capacity = 1000000, new capacity = 50
I can't edit the code in the EJB (automatically generated to give access to another system) but can edit the ejb-jar.xml and add a jboss.xml. I'm looking at this but still getting the same error when I try and run the client.
Have done this successfully on Weblogic by first running ejbc on the automatically generated EJB before deploying it. I can also generate and run the jboss EJB Interest example on my PC without any problems.
I have the same problem. The lookup is fine, and won't work if I try anything else. I can use the returned home object to do findByPrimaryKey. It bombs out at create.
Now working - problem was in the ejb-jar.xml. env-entry with a name of "java.rmi.server.hostname" was not picked-up. If I edited the entry to "java/rmi/server/hostname" then all worked fine and my simple test client could connect to the ERP system.
Don't know why this was or why the automatically generated bean should have this name but is working now..
Thanks for your help.