Unable to lookup on EAP 7 throwing javax.naming.NamingException: Unable to invoke lookup, status=WAITING exception

Solution Unverified - Updated -

Issue

  • I am running one application on tomcat which connects to JMS broker which is hosted on JBoss EAP 7. The code used to work when I was using EAP 6 version of jboss-client.jar to connect. After upgrading the jar, it seems to start throwing this exception. Could you please help me on this issue. The same code piece works in local eclipse. But that does not work in the tomcat environment.
Caused by: javax.naming.NamingException: Unable to invoke lookup, status=WAITING at org.jboss.naming.remote.protocol.v1.Protocol$1.execute(Protocol.java:98) at org.jboss.naming.remote.protocol.v1.RemoteNamingStoreV1.lookup(RemoteNamingStoreV1.java:95) at org.jboss.naming.remote.client.HaRemoteNamingStore$1.operation(HaRemoteNamingStore.java:276) at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:132) at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:272) at org.jboss.naming.remote.client.RemoteContext.lookupInternal(RemoteContext.java:104) at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:93) at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:146) at javax.naming.InitialContext.lookup(InitialContext.java:417)

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 7

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.