Race condition during server start-up - RA not deployed in JBoss EAP 6

Solution Verified - Updated -


  • We have run into the following bugs in our testing of JBoss EAP version 6.1.0:

  • We defined our resource adapter in the resource-adapters subsystem, it should bind a JNDB name MyRANoTx, which another one of our deployments is trying to lookup.

        <subsystem xmlns="urn:jboss:domain:resource-adapters:1.1">
                <resource-adapter id="MyRA.rar">
                        <connection-definition class-name="com.jboss.examples.connector.MyManagedConnectionFactory" jndi-name="java:/MyRANoTx" pool-name=MyRANoTx"/>

  • The deployment fails sometimes because the resource-adapter has not bound into JNDI in time:
JBAS014775:    New missing/unsatisfied dependencies:
      service jboss.naming.context.java.TIPRANoTx (missing) dependents: [service jboss.naming.context.java.comp.MyRATest.MyRATest.MyRATest.env.MyRANoTx] 

03:38:34,143 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on
03:38:34,143 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on
03:38:34,143 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14) started (with errors) in 4816ms - Started 233 of 306 services (5 services failed or missing dependencies, 67 services are passive or on-demand)
  • connection-definition are not registered in time in JBoss EAP 6.2.0


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

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

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