We are currently using version 4.0.0, although I will be migrating to version
4.03 once I fix an unrelated problem in another module.
Here is the JNDI section of the conf/jboss-service.xml file :
true
1099
1098
I have a server with 2 ethernet addresses (192.168.x.x) and (10.10.0.x).
My application wants to access a stateless-session bean from the JBoss instance
running on this server. I can perform a Context:lookup to get the Home
interface of the EJB and perform method calls from the 192.168 side of t
This is a problem caused by the clustering code, right ? Can we disable
clustering to get around this problem, or is it truly necessary to use a
different name in the remote's JNDI ?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872738#3872738
Reply to the
