RE: calling ejb on another app server
We do tomcat (servlet) to remote jboss (EJB). Isn't JNDI usually bound to 1099 ? Also, is usually a critical port. Some ISPs block it. Remapping to 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]
RE: calling ejb on another app server
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, is usually a critical port. Some ISPs block it. Remapping to 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]
RE: calling ejb on another app server
Another critical jboss element is setting jnp rmi port to something, here it's 34159 I set it in jboss/server/default/conf/jboss-service.xml attribute name=Properties invokerServletPath=http://localhost:8080/invoker/JMXInvokerServlet jnp.rmiPort=34159 /attribute like that. You may also need to make jboss bind to your WAN ip. Add these options in run.bat: -Djava.rmi.server.hostname=JBOSS-WAN-STATIC-IP -Djava.rmi.server.useLocalHostname=false Sincerely, Neil Upfalow -Original Message- From: Eric J Kaplan [mailto:[EMAIL PROTECTED] Sent: Thursday, April 07, 2005 1:36 PM To: 'Tomcat Users List' Subject: RE: calling ejb on another app server 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, is usually a critical port. Some ISPs block it. Remapping to 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]
Re: calling ejb on another app server
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, is usually a critical port. Some ISPs block it. Remapping to 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]
RE: calling ejb on another app server
That's the strange thing because I print out the environment of the context being used at the time the failure occurs and it does seem to be taking it from my jndi.properties file! Of course, simply printing out the context is different than what the context may ACTUALLY be doing. Regards Eric -Original Message- From: N G [mailto:[EMAIL PROTECTED] Sent: Thursday, April 07, 2005 1:54 PM To: Tomcat Users List Subject: Re: calling ejb on another app server 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, is usually a critical port. Some ISPs block it. Remapping to 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: calling ejb on another app server
Neil I'll give it a try, though note that we have been using jboss for a few years and have plenty of standalone apps communicating fine with jboss through the same api as that used by the servlet. Regards Eric -Original Message- From: Neil Upfalow [mailto:[EMAIL PROTECTED] Sent: Thursday, April 07, 2005 1:53 PM To: 'Tomcat Users List' Subject: RE: calling ejb on another app server Another critical jboss element is setting jnp rmi port to something, here it's 34159 I set it in jboss/server/default/conf/jboss-service.xml attribute name=Properties invokerServletPath=http://localhost:8080/invoker/JMXInvokerServlet jnp.rmiPort=34159 /attribute like that. You may also need to make jboss bind to your WAN ip. Add these options in run.bat: -Djava.rmi.server.hostname=JBOSS-WAN-STATIC-IP -Djava.rmi.server.useLocalHostname=false Sincerely, Neil Upfalow -Original Message- From: Eric J Kaplan [mailto:[EMAIL PROTECTED] Sent: Thursday, April 07, 2005 1:36 PM To: 'Tomcat Users List' Subject: RE: calling ejb on another app server 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, is usually a critical port. Some ISPs block it. Remapping to 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
