If you are not getting some communication exception when you change the port number to the wrong port, it tells me that your jndi.properties are being ignored.
As you pointed out, it's probably returning an instance of Tomcat readonly JNDI. I suggest you load your jndi.properties explicitely use new InitialContext(properties) constructor. This should for sure force it to try to connect to the proper JNDI provider. HTH, NG. On Apr 7, 2005 1:35 PM, Eric J Kaplan <[EMAIL PROTECTED]> wrote: > Yes it is. I changed it in my jndi.properties file to see if I would get a > different error. It was originally 1099. > > Given that, and the fact that you have this working (we are also using > jboss) do you have any other ideas? I assume you are on tomcat 5x or > greater? > > My setup is pretty vanilla. I'm sure it's just a configuration switch, but > not sure which one. > > Regards > > Eric > > -----Original Message----- > From: Neil Upfalow [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 07, 2005 1:30 PM > To: 'Tomcat Users List' > Subject: RE: calling ejb on another app server > > We do tomcat (servlet) to remote jboss (EJB). > Isn't JNDI usually bound to 1099 ? > Also, 4444 is usually a critical port. Some ISPs block it. Remapping to > 8888 usually solves this problem. > > Hope it helps. > > Sincerely, > Neil Upfalow > > -----Original Message----- > From: Eric J Kaplan [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 07, 2005 1:23 PM > To: 'Tomcat Users List' > Subject: calling ejb on another app server > > Does anyone have any experience getting a servlet that calls an ejb on a > different application server to work, running tomcat 5.0.28? > > I know we got this to work under 3.x a while ago. > > At this point I feel like we've tried everything but we always get that > name > "ejb" is not bound in this context. I even tried changing my > jndi.properties > to point to an invalid host, and although when I print out the > environment > for the context just before looking up the bean it indeed says that the > naming provider url is foo:1066, I don't get a communication exception, > I > get that the ejb context is not bound. My suspicion is it is going > against a > jndi server running within tomcat that doesn't have the ejb context > bound. > > Help would be appreciated, we've been floundering for a couple of days. > > Regards > > Eric > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
