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

Updated 2015-07-09T01:35:45+00:00

Issue

  • 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-adapters>
                <resource-adapter id="MyRA.rar">
                    <archive>
                        MyRA.rar
                    </archive>
                    <transaction-support>NoTransaction</transaction-support>
                    <connection-definitions>
                        <connection-definition class-name="com.jboss.examples.connector.MyManagedConnectionFactory" jndi-name="java:/MyRANoTx" pool-name=MyRANoTx"/>
                    </connection-definitions>
                </resource-adapter>
            </resource-adapters>
        </subsystem>

  • 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 http://127.0.0.1:9990/management
03:38:34,143 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
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

Environment

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

Subscriber content preview. For full access to the Red Hat Knowledgebase, please log in.

Not a subscriber? Learn more about the benefits of Red Hat Subscriptions.