JNDI - TCP 1099 Timeout

[will.tatam]

Does CR1 have support for remote JNDI ? I just get connection timeouts when trying to do remote JNDI lookups from my RMI client

[will.tatam]

I am seeing the same issues with AS 7.1.0.Beta1b when trying to connect my ejb client to AS7. I have changed the JNDI url pattern from that of AS5.1 to the new forms I see in the app server logs, but jndi just times out

Caused by: javax.naming.CommunicationException: Could not obtain connection to any of these urls: jnp://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/127.0.0.1:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection timed out]]]

          at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1763)

          at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:693)

          at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)

          at javax.naming.InitialContext.lookup(InitialContext.java:409)

          at catalog.util.JNDICache.getController(JNDICache.java:233)

          ... 21 more

Caused by: javax.naming.CommunicationException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection timed out]]

          at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:335)

          at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1734)

          ... 25 more

Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection timed out]

          at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:305)

          ... 26 more

Caused by: java.net.ConnectException: Connection timed out

          at java.net.PlainSocketImpl.socketConnect(Native Method)

          at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:327)

          at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:193)

          at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:180)

          at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:384)

          at java.net.Socket.connect(Socket.java:546)

          at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:97)

          at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:82)

          at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:301)

          ... 26 more

[jaikiran]

JNDI isn't exposed remotely via RMI. i.e. the port you are using is of no use. For EJB invocations from a remote client, see this https://docs.jboss.org/author/display/AS71/EJB+invocations+from+a+remote+client+using+JNDI

[will.tatam]

Thanks. All up and running making calls to the server. Just need to work out how to pass the connection settings using properties set in jnlp rather than hard baked jboss-ejb-client.properties

[jaikiran]

Will Tatam wrote:

Just need to work out how to pass the connection settings using properties set in jnlp rather than hard baked jboss-ejb-client.properties

Can you explain a bit more about that usecase? I have seen one other user asking for something similar http://community.jboss.org/thread/175451?tstart=60. Is it the same?

[will.tatam]

I have added notes to the JIRA task