[JNDI/Naming/Network] - javax.naming.CommunicationException at localhost:1099
by argonist
Two JBOSS-instance started on one machine and it worked fine. The Web-application and EJB-application are deployed on both JBOSS-Instance and web-application are invoked by browser. The Web-application worked finely with default ports on first JBOSS-instance, but did not work with different ports on second JBOSS-instance (./run.sh -c node1).
anonymous wrote :
| 22:21:40,696 INFO [[/PonteWeb]] No state saving method defined, assuming default server state saving
| 22:21:46,517 INFO [STDOUT] unable to get reference
| 22:21:46,517 ERROR [STDERR] javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused]]]
| 22:21:46,519 ERROR [STDERR] at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1414)
| 22:21:46,519 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:594)
| 22:21:46,520 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
| 22:21:46,520 ERROR [STDERR] at javax.naming.InitialContext.lookup(InitialContext.java:351)
| 22:21:46,520 ERROR [STDERR] at de.kirchedlau.ponte.MyNavigationMenu.getSession(MyNavigationMenu.java:116)
| 22:21:46,520 ERROR [STDERR] at de.kirchedlau.ponte.MyNavigationMenu.(MyNavigationMenu.java:47)
| 22:21:46,520 ERROR [STDERR] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
| 22:21:46,521 ERROR [STDERR] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
|
It should be connected to server localhost: 1199, but the web-application looked for port 1099.
telnet localhost 1199 worked finely.
jndi.properties
| java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
| java.naming.provider.url=jnp://localhost:1199
| java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
|
jboss-service.xml (ports_1 uncomment)
|
| <mbean code="org.jboss.services.binding.ServiceBindingManager"
| name="jboss.system:service=ServiceBindingManager">
| <attribute name="ServerName">ports-01</attribute>
| <attribute name="StoreURL">${jboss.home.url}/docs/examples/binding-manager/sample-bindings.xml</attribute>
| <attribute name="StoreFactoryClassName">
| org.jboss.services.binding.XMLServicesStoreFactory
| </attribute>
| </mbean>
|
OS Suse 10.2
JBOSS 4.0.5.GA
Thanks
Cheers
Manu
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033835#4033835
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033835
19 years