Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via runawfe by ansvrn
, 1 year ago
javax.naming.CommunicationException: Could not obtain connection to any of these urls: 192.168.1.1:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out  \[Root exception is javax.naming.CommunicationException
via runawfe by mgaido
, 1 year ago
javax.naming.CommunicationException: Receive timed out \[Root exception is java.net.SocketTimeoutException: Receive timed out\]
via runawfe by vromav
, 1 year ago
javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:10099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException
via runawfe by gabrigenius
, 1 year ago
javax.naming.NameNotFoundException: af not bound
javax.naming.CommunicationException: Could not obtain connection to any of these urls: 192.168.1.1:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out  \[Root exception is javax.naming.CommunicationException: Failed to connect to server 192.168.1.1:1099 \[Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server 192.168.1.1:1099 \]\]  	at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1562)	at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:634)	at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)	at javax.naming.InitialContext.lookup(Unknown Source)	at ru.runa.af.delegate.impl.RemoteDelegate.getHomeObject(RemoteDelegate.java:122)	at ru.runa.af.delegate.impl.RemoteDelegate.initHomeObject(RemoteDelegate.java:113)