Having yet another problem with the configuration in WebSphere.
I have a Standalone java client that looks up and EJB - well that's what it's supposed to do anyway. The lookup fails. I have m ORB Bootstrap running on port 2809. Here's the code I use to get the initial context:
I get the following exception:
Why, at the bottom of this message, is it showing my port as 9100?
[ November 10, 2005: Message edited by: Michael Valentino ] [ November 10, 2005: Message edited by: Michael Valentino ]
But when I try to do the lookup from a stand-alone Java client, i get the same error message displayed in the first message in this Topic. What kind of black magic is this UTC doing that I'm not doing in my client?
LOL, the UTC is an excellent test of whether a service is working, especially for JNDI objects, so congrats that at least works.
I'm thinking your missing something quite obvious with your test code, but I can't say for sure I know what it is without being deep in your setup. Just try removing and scaling back the data until you get something that works is the best I can tell you.
Sorry! [ November 10, 2005: Message edited by: Scott Selikoff ]
I'm starting to think that the issue here is a network issue. If I access an EJB web service from a Servlet or another EJB client, all works well. It's only when I try to access the EJB from a client running in another instance of the JVM - servlet, or standalone client - does the JNDI lookup fail.
When you install the WAS test environment, did you put for the server name "localhost" or "computername.domainname" ?
Also, I see you are using java/comp to do the lookup. From a stand alone client, you need to use the fully qualified JNDI name. If you want to use a J2EE applicaiton client, then you need to run the client container: