javax.naming.NameNotFoundException: DefaultJMSProvider not bound

Solution Unverified - Updated -

Issue

After configuring JBM XA Recovery Module, we see following logs in server.log . Usually this occurs when we try to start or stop the server.

> [Thread- Thread-5] ERROR [org.jboss.jms.server.recovery.MessagingXAResourceWrapper:getDelegate] \*\*\*\\*\*\*\\*\*\*\\*\*\*\\*\*\*\\*\*\*\\*\*\*\\*\*\*\\*\*\*\\*\****Failed to connect to server  
> javax.naming.NameNotFoundException: DefaultJMSProvider not bound  
> at org.jnp.server.NamingServer.getBinding(NamingServer.java:581)  
> at org.jnp.server.NamingServer.getBinding(NamingServer.java:589)  
> at org.jnp.server.NamingServer.getObject(NamingServer.java:595)  
> at org.jnp.server.NamingServer.lookup(NamingServer.java:342)  
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:667)  
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)  
> at javax.naming.InitialContext.lookup(InitialContext.java:392)  
  • Start up of server is failing. The server with hostname host01 in one of the test environments is failing. Whenever we run the custom start up script, it asks for the credentials and abruptly displays the message "JBoss startup failed"(i.e custom log message via custom startup script).

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 4.3
    • 5.0
  • Red Hat JBoss SOA Platform (SOA-P)
    • 4.3
    • 5.0
  • JBoss Messaging

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.