3 Replies Latest reply on Mar 1, 2015 2:59 PM by Levent Tutar

    Distributed transactions not working for MDB (EJB 2.1) with JBOSS EAP 6.1 (JBOSS AS 7.2.0) for IBM MQ 7.x Client Jars

    Chintan Modha Newbie

      Hi All,

       

      I'm facing an issue with my MDB during the deployment, The current MDB is working fine on WebSphere 5.1.x server. As a part of a migration project, we are migrating this MDB on JBOSS EAP 6.1 which comes along with JBOSS AS 7.2.0 final version. To what I see is that I'm facing issue with the container transaction, during the deployment of the EJB.jar .

       

      Here's the exception stack trace . As per the exception it says that "Distributed transactions are not available in CLIENT mode", I've spent lot of days debugging this issue, but not having any luck. I'll really appreciate any insight on resolving this issue.

       

      Thanks,

      Chintan.

       

       

      16:01:57,394 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 59) MSC000001: Failed to start service jboss.deployment.subunit."CSIEAR.ear"."CSIspsmqEJB.jar".component.COOLMsgProcessorMDB.START: org.jboss.msc.service.StartException in service jboss.deployment.subunit."CSIEAR.ear"."CSIspsmqEJB.jar".component.COOLMsgProcessorMDB.START: java.lang.RuntimeException: com.ibm.mq.connector.DetailedResourceException: MQJCA1004: Distributed transactions are unavailable., error code: MQJCA1004 An attempt was made to use distributed transactions in an environment where they are not available. Make sure that the WebSphere MQ extended transactional client is installed if required, or use a bindings connection.
          at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
          at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [rt.jar:1.6.0_30]
          at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_30]
          at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_30]
          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
          at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
          at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final-redhat-1.jar:2.1.0.Final-redhat-1]
      Caused by: java.lang.RuntimeException: com.ibm.mq.connector.DetailedResourceException: MQJCA1004: Distributed transactions are unavailable., error code: MQJCA1004 An attempt was made to use distributed transactions in an environment where they are not available. Make sure that the WebSphere MQ extended transactional client is installed if required, or use a bindings connection.
          at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.start(MessageDrivenComponent.java:180)
          at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
          ... 7 more
      Caused by: com.ibm.mq.connector.DetailedResourceException: MQJCA1004: Distributed transactions are unavailable., error code: MQJCA1004 An attempt was made to use distributed transactions in an environment where they are not available. Make sure that the WebSphere MQ extended transactional client is installed if required, or use a bindings connection.
          at com.ibm.mq.connector.services.JCAExceptionBuilder.buildException(JCAExceptionBuilder.java:124)
          at com.ibm.mq.connector.services.JCAExceptionBuilder.buildException(JCAExceptionBuilder.java:86)
          at com.ibm.mq.connector.ResourceAdapterImpl.endpointActivation(ResourceAdapterImpl.java:417)
          at org.jboss.jca.core.rar.EndpointImpl.activate(EndpointImpl.java:164) [ironjacamar-core-impl-1.0.17.Final-redhat-1.jar:1.0.17.Final-redhat-1]
          at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.start(MessageDrivenComponent.java:178)
          ... 8 more
      

       

      I'll also list out all my configuration that I've used for JBOSS 6.1 EAP and for the MDB in the below manner.

       

      1) IBM MQ Resource adapter .

      2) standalone-full.xml

      3) ejb-jar.xml

      4) jboss-ejb3.xml

      5) server.log file

       

      1) IBM MQ Resource Adapter:

       

       

      2) Standalon-full.xml

      • Here is the xml snippet for resource-adapter subsystems, found with in standalone-full.xml

       

      <subsystem xmlns="urn:jboss:domain:resource-adapters:1.1">
            <resource-adapters>
                     <resource-adapter>
                          <archive>wmq.jmsra.rar</archive>
                          <transaction-support>XATransaction</transaction-support>
                          <config-property name="traceEnabled">true</config-property>
                          <config-property name="traceLevel">3</config-property>
                          <connection-definitions>
                              <connection-definition class-name="com.ibm.mq.connector.outbound.ManagedQueueConnectionFactoryImpl" jndi-name="java:jboss/jms/COOLJMSQueueConnectionFactory" enabled="true" use-java-context="true" pool-name="COOLJMSQueueConnectionFactoryPool">
                                  <config-property name="port">1417</config-property>
                                  <config-property name="hostName">XX.XX.XX.XXX</config-property>
                                  <config-property name="channel">MQ.CLIENT</config-property>
                                  <config-property name="transportType">CLIENT</config-property>
                                  <config-property name="queueManager">MYQMGR</config-property>
                                  <xa-pool>
                                      <min-pool-size>1</min-pool-size>
                                      <max-pool-size>10</max-pool-size>
                                  </xa-pool>
                              </connection-definition>
                          </connection-definitions>
                          <admin-objects>
                              <admin-object class-name="com.ibm.mq.connector.outbound.MQQueueProxy" jndi-name="java:jboss/jms/COOLJMSInboundQueue" enabled="true" use-java-context="true" pool-name="COOLJMSInboundQueuePool">
                                  <config-property name="baseQueueName">INBOUND.QUEUE.TEST</config-property>
                                  <config-property name="baseQueueManagerName">MYQMGR</config-property>
                              </admin-object>
                          </admin-objects>
                      </resource-adapter>
                  </resource-adapters>
              </subsystem>
      

       

      • Here's the xml snippet for ejb3 sub-system, found with in standalone-full.xml

           

      <subsystem xmlns="urn:jboss:domain:ejb3:1.4">
                  <session-bean>
                      <stateless>
                          <bean-instance-pool-ref pool-name="slsb-strict-max-pool"/>
                      </stateless>
                      <stateful default-access-timeout="5000" cache-ref="simple"/>
                      <singleton default-access-timeout="5000"/>
                  </session-bean>
                  <mdb>
                      <resource-adapter-ref resource-adapter-name="wmq.jmsra.rar" />
                      <bean-instance-pool-ref pool-name="mdb-strict-max-pool" />
                  </mdb>            
                  <pools>
                      <bean-instance-pools>
                          <strict-max-pool name="slsb-strict-max-pool" max-pool-size="20" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
                          <strict-max-pool name="mdb-strict-max-pool" max-pool-size="20" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
                      </bean-instance-pools>
                  </pools>
                  <caches>
                      <cache name="simple" aliases="NoPassivationCache"/>
                      <cache name="passivating" passivation-store-ref="file" aliases="SimpleStatefulCache"/>
                  </caches>
                  <passivation-stores>
                      <file-passivation-store name="file"/>
                  </passivation-stores>
                  <async thread-pool-name="default"/>
                  <timer-service thread-pool-name="default">
                      <data-store path="timer-service-data" relative-to="jboss.server.data.dir"/>
                  </timer-service>
                  <remote connector-ref="remoting-connector" thread-pool-name="default"/>
                  <thread-pools>
                      <thread-pool name="default">
                          <max-threads count="10"/>
                          <keepalive-time time="100" unit="milliseconds"/>
                      </thread-pool>
                  </thread-pools>
                  <iiop enable-by-default="false" use-qualified-name="false"/>
                  <default-security-domain value="other"/>
                  <default-missing-method-permissions-deny-access value="true"/>
              </subsystem>
      

       


      • Also, I have checked through the server logs that indeed I'm using standalone-full.xml for my server startup and not the regular standalone.xml 

            

      sun.java.command = org.jboss.modules.Main -mp F:/jboss-eap-6.1/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b localhost --server-config=standalone-full.xml
      

       

           

        3) ejb-jar.xml : Here's the snippet of the ejb-jar.xml

       

       

      <?xml version="1.0" encoding="UTF-8"?>
      <ejb-jar id="ejb-jar_ID" version="2.1" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
          <display-name>CSIspsmqEJB</display-name>    
          <enterprise-beans>    
              <message-driven id="COOLMsgProcessorMDB">
                  <ejb-name>COOLMsgProcessorMDB</ejb-name>
                  <ejb-class>com.scholastic.msgejbs.COOLMsgProcessorMDBBean</ejb-class>
                  <messaging-type>javax.jms.MessageListener</messaging-type>
                  <transaction-type>Container</transaction-type>    
                  <activation-config>
                      <activation-config-property>
                          <activation-config-property-name>destinationType</activation-config-property-name>
                          <activation-config-property-value>javax.jms.Queue</activation-config-property-value>
                      </activation-config-property>
                      <activation-config-property>
                          <activation-config-property-name>destination</activation-config-property-name>
                          <activation-config-property-value>>INBOUND.QUEUE.TEST</activation-config-property-value>
                      </activation-config-property>
                      <!-- <activation-config-property>
                          <activation-config-property-name>useJNDI</activation-config-property-name>
                          <activation-config-property-value>false</activation-config-property-value>
                      </activation-config-property> -->                
                      <activation-config-property>
                          <activation-config-property-name>channel</activation-config-property-name>
                          <activation-config-property-value>MQ.CLIENT</activation-config-property-value>
                      </activation-config-property>                
                      <activation-config-property>
                          <activation-config-property-name>hostName</activation-config-property-name>
                          <activation-config-property-value>XX.XX.XX.XXX</activation-config-property-value>
                      </activation-config-property>                
                      <activation-config-property>
                          <activation-config-property-name>queueManager</activation-config-property-name>
                          <activation-config-property-value>MYQMGR</activation-config-property-value>
                      </activation-config-property>                
                      <activation-config-property>
                          <activation-config-property-name>port</activation-config-property-name>
                          <activation-config-property-value>1417</activation-config-property-value>
                      </activation-config-property>                
                      <activation-config-property>
                          <activation-config-property-name>transportType</activation-config-property-name>
                          <activation-config-property-value>CLIENT</activation-config-property-value>                    
                      </activation-config-property>
                  </activation-config>        
              </message-driven>        
          </enterprise-beans>
          <assembly-descriptor>
          </assembly-descriptor>
      </ejb-jar>
      

       

      4) jboss-ejb3.xml : Here's the snippet of the jboss-ejb3.xml that I've used.


         

      <?xml version="1.1" encoding="UTF-8"?>
      <jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee"
                     xmlns="http://java.sun.com/xml/ns/javaee"
                     xmlns:mdb="urn:resource-adapter-binding"
                     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                     xmlns:c="urn:clustering:1.0"
                     xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd"
                     version="3.1"
                     impl-version="2.0">   
          <assembly-descriptor>         
              <mdb:resource-adapter-binding>
                  <ejb-name>COOLMsgProcessorMDB</ejb-name>
                  <mdb:resource-adapter-name>wmq.jmsra.rar</mdb:resource-adapter-name>
              </mdb:resource-adapter-binding>
          </assembly-descriptor>
      </jboss:ejb-jar>
      

       

      5) server.log : Here's the whole server.log file along with the exception stack trace.

       

      16:01:36,406 INFO  [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final-redhat-1
      16:01:36,813 INFO  [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1
      16:01:36,891 INFO  [org.jboss.as] (MSC service thread 1-1) JBAS015899: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) starting
      16:01:43,142 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found CSIEAR.ear in deployment directory. To trigger deployment create a file called CSIEAR.ear.dodeploy
      16:01:43,173 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
      16:01:43,251 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 35) JBAS010280: Activating Infinispan subsystem.
      16:01:43,251 INFO  [org.jboss.as.jacorb] (ServerService Thread Pool -- 36) JBAS016300: Activating JacORB Subsystem
      16:01:43,267 INFO  [org.xnio] (MSC service thread 1-2) XNIO Version 3.0.7.GA-redhat-1
      16:01:43,407 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 43) JBAS012605: Activated the following JSF Implementations: [main, 1.2]
      16:01:43,579 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 47) JBAS011800: Activating Naming Subsystem
      16:01:43,798 INFO  [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.0.7.GA-redhat-1
      16:01:43,798 INFO  [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 3.2.16.GA-redhat-1
      16:01:43,861 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 52) JBAS013171: Activating Security Subsystem
      16:01:43,908 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 56) JBAS015537: Activating WebServices Extension
      16:01:44,548 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 31) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
      16:01:44,564 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 31) JBAS010403: Deploying JDBC-compliant driver class com.ibm.db2.jcc.DB2Driver (version 4.0)
      16:01:44,564 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 31) JBAS010403: Deploying JDBC-compliant driver class com.ibm.db2.jcc.DB2Driver (version 4.0)
      16:01:45,642 INFO  [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service
      16:01:45,642 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.17.Final-redhat-1)
      16:01:45,548 INFO  [org.jboss.as.security] (MSC service thread 1-1) JBAS013170: Current PicketBox version=4.0.17.Final-redhat-1
      16:01:45,830 INFO  [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.1.3.Final-redhat-3
      16:01:45,845 INFO  [org.jboss.jaxr] (MSC service thread 1-1) JBAS014000: Started JAXR subsystem, binding JAXR connection factory into JNDI as: java:jboss/jaxr/ConnectionFactory
      16:01:45,908 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default]
      16:01:45,908 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/comp/env/mail/ScholasticMailSession]
      16:01:45,986 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) JBAS015012: Started FileSystemDeploymentService for directory F:\jboss-eap-6.1\standalone\deployments
      16:01:46,002 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "CSIEAR.ear" (runtime-name: "CSIEAR.ear")
      16:01:46,002 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "wmq.jmsra.rar" (runtime-name: "wmq.jmsra.rar")
      16:01:46,580 INFO  [org.apache.coyote.http11] (MSC service thread 1-2) JBWEB003001: Coyote HTTP/1.1 initializing on : http-localhost/192.168.181.152:8080
      16:01:46,752 INFO  [org.apache.coyote.http11] (MSC service thread 1-2) JBWEB003000: Coyote HTTP/1.1 starting on: http-localhost/192.168.181.152:8080
      16:01:46,986 WARN  [jacorb.codeset] (MSC service thread 1-2) Warning - unknown codeset (Cp1252) - defaulting to ISO-8859-1
      16:01:47,002 INFO  [org.apache.coyote.http11] (MSC service thread 1-1) JBWEB003001: Coyote HTTP/1.1 initializing on : http-localhost/192.168.181.152:8443
      16:01:47,002 INFO  [org.apache.coyote.http11] (MSC service thread 1-1) JBWEB003000: Coyote HTTP/1.1 starting on: http-localhost/192.168.181.152:8443
      16:01:47,049 INFO  [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016330: CORBA ORB Service started
      16:01:47,393 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "null" (runtime-name: "CSIspsmqWeb.war")
      16:01:47,393 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "null" (runtime-name: "CSIspsmqEJB.jar")
      16:01:47,408 INFO  [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 127.0.0.1:9999
      16:01:47,439 INFO  [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 192.168.181.152:4447
      16:01:48,877 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry ldap.jar in /F:/jboss-eap-6.1/bin/content/wmq.jmsra.rar/com.ibm.mqjms.jar  does not point to a valid jar for a Class-Path reference.
      16:01:48,877 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry jndi.jar in /F:/jboss-eap-6.1/bin/content/wmq.jmsra.rar/com.ibm.mqjms.jar  does not point to a valid jar for a Class-Path reference.
      16:01:48,877 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry fscontext.jar in /F:/jboss-eap-6.1/bin/content/wmq.jmsra.rar/com.ibm.mqjms.jar  does not point to a valid jar for a Class-Path reference.
      16:01:48,877 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry providerutil.jar in /F:/jboss-eap-6.1/bin/content/wmq.jmsra.rar/com.ibm.mqjms.jar  does not point to a valid jar for a Class-Path reference.
      16:01:48,893 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry rmm.jar in /F:/jboss-eap-6.1/bin/content/wmq.jmsra.rar/com.ibm.msg.client.wmq.v6.jar  does not point to a valid jar for a Class-Path reference.
      16:01:48,893 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry CL3Export.jar in /F:/jboss-eap-6.1/bin/content/wmq.jmsra.rar/com.ibm.msg.client.wmq.v6.jar  does not point to a valid jar for a Class-Path reference.
      16:01:48,893 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry CL3Nonexport.jar in /F:/jboss-eap-6.1/bin/content/wmq.jmsra.rar/com.ibm.msg.client.wmq.v6.jar  does not point to a valid jar for a Class-Path reference.
      16:01:48,893 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry connector.jar in /F:/jboss-eap-6.1/bin/content/wmq.jmsra.rar/com.ibm.mq.jar  does not point to a valid jar for a Class-Path reference.
      16:01:48,908 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry jms.jar in /F:/jboss-eap-6.1/bin/content/wmq.jmsra.rar/com.ibm.msg.client.jms.jar  does not point to a valid jar for a Class-Path reference.
      16:01:48,908 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry jta.jar in /F:/jboss-eap-6.1/bin/content/wmq.jmsra.rar/com.ibm.mq.jmqi.jar  does not point to a valid jar for a Class-Path reference.
      16:01:48,987 INFO  [org.jboss.as.jacorb] (MSC service thread 1-1) JBAS016328: CORBA Naming Service started
      16:01:49,330 INFO  [org.hornetq.core.server] (MSC service thread 1-1) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=F:\jboss-eap-6.1\standalone\data\messagingjournal,bindingsDirectory=F:\jboss-eap-6.1\standalone\data\messagingbindings,largeMessagesDirectory=F:\jboss-eap-6.1\standalone\data\messaginglargemessages,pagingDirectory=F:\jboss-eap-6.1\standalone\data\messagingpaging)
      16:01:49,346 INFO  [org.hornetq.core.server] (MSC service thread 1-1) HQ221006: Waiting to obtain live lock
      16:01:49,393 INFO  [org.hornetq.core.server] (MSC service thread 1-1) HQ221013: Using NIO Journal
      16:01:50,081 INFO  [org.hornetq.core.server] (MSC service thread 1-1) HQ221034: Waiting to obtain live lock
      16:01:50,081 INFO  [org.hornetq.core.server] (MSC service thread 1-1) HQ221035: Live Server Obtained live lock
      16:01:51,784 INFO  [org.hornetq.core.server] (MSC service thread 1-1) HQ221020: Started Netty Acceptor version 3.6.2.Final-redhat-1-c0d783c 192.168.181.152:5455 for CORE protocol
      16:01:51,800 INFO  [org.hornetq.core.server] (MSC service thread 1-1) HQ221020: Started Netty Acceptor version 3.6.2.Final-redhat-1-c0d783c 192.168.181.152:5445 for CORE protocol
      16:01:51,800 INFO  [org.hornetq.core.server] (MSC service thread 1-1) HQ221007: Server is now live
      16:01:51,800 INFO  [org.hornetq.core.server] (MSC service thread 1-1) HQ221001: HornetQ Server version 2.3.1.Final (Wild Hornet, 123) [f255ad30-011c-11e3-9336-35cda25c9872] 
      16:01:51,862 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
      16:01:51,862 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/jdbc/DB2DataSource]
      16:01:51,862 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/jdbc/DB2ContactHistoryDS]
      16:01:51,940 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 58) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
      16:01:51,940 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
      16:01:52,018 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-1) JBAS010406: Registered connection factory java:/JmsXA
      16:01:52,065 INFO  [org.hornetq.ra] (MSC service thread 1-1) HornetQ resource adaptor started
      16:01:52,065 INFO  [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-1) IJ020002: Deployed: file://RaActivatorhornetq-ra
      16:01:52,675 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-1) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
      16:01:52,753 INFO  [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-1) IJ020001: Required license terms for file:/F:/jboss-eap-6.1/standalone/tmp/vfs/temp1ce476af1686b8e9/wmq.jmsra.rar-b119192864c9c82c/contents/
      16:01:53,253 INFO  [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-1) IJ020001: Required license terms for file:/F:/jboss-eap-6.1/standalone/tmp/vfs/temp1ce476af1686b8e9/wmq.jmsra.rar-b119192864c9c82c/contents/
      16:01:53,269 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-1) JBAS010406: Registered connection factory java:jboss/jms/COOLJMSQueueConnectionFactory
      16:01:53,269 WARN  [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-1) IJ020016: Missing <recovery> element. XA recovery disabled for: java:jboss/jms/COOLJMSQueueConnectionFactory
      16:01:53,394 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-1) JBAS010405: Registered admin object at java:jboss/jms/COOLJMSInboundQueue
      16:01:56,941 INFO  [org.jboss.web] (ServerService Thread Pool -- 58) JBAS018210: Register web context: /CSIspsmqWeb
      
      16:01:57,301 INFO  [stdout] (MSC service thread 1-1) MQJCA4005:Distributed transactions are not available in client mode.
      
      16:01:57,301 INFO  [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-1) IJ020002: Deployed: file:/F:/jboss-eap-6.1/standalone/tmp/vfs/temp1ce476af1686b8e9/wmq.jmsra.rar-b119192864c9c82c/contents/
      16:01:57,332 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-2) JBAS010401: Bound JCA ConnectionFactory [java:jboss/jms/COOLJMSQueueConnectionFactory]
      16:01:57,332 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-2) JBAS010401: Bound JCA AdminObject [java:jboss/jms/COOLJMSInboundQueue]
      16:01:57,363 INFO  [org.jboss.as.ejb3] (MSC service thread 1-1) JBAS014142: Started message driven bean 'COOLMsgProcessorMDB' with 'wmq.jmsra' resource adapter
      16:01:57,394 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 59) MSC000001: Failed to start service jboss.deployment.subunit."CSIEAR.ear"."CSIspsmqEJB.jar".component.COOLMsgProcessorMDB.START: org.jboss.msc.service.StartException in service jboss.deployment.subunit."CSIEAR.ear"."CSIspsmqEJB.jar".component.COOLMsgProcessorMDB.START: java.lang.RuntimeException: com.ibm.mq.connector.DetailedResourceException: MQJCA1004: Distributed transactions are unavailable., error code: MQJCA1004 An attempt was made to use distributed transactions in an environment where they are not available. Make sure that the WebSphere MQ extended transactional client is installed if required, or use a bindings connection.
          at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
          at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [rt.jar:1.6.0_30]
          at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_30]
          at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_30]
          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
          at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
          at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final-redhat-1.jar:2.1.0.Final-redhat-1]
      Caused by: java.lang.RuntimeException: com.ibm.mq.connector.DetailedResourceException: MQJCA1004: Distributed transactions are unavailable., error code: MQJCA1004 An attempt was made to use distributed transactions in an environment where they are not available. Make sure that the WebSphere MQ extended transactional client is installed if required, or use a bindings connection.
          at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.start(MessageDrivenComponent.java:180)
          at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
          ... 7 more
      Caused by: com.ibm.mq.connector.DetailedResourceException: MQJCA1004: Distributed transactions are unavailable., error code: MQJCA1004 An attempt was made to use distributed transactions in an environment where they are not available. Make sure that the WebSphere MQ extended transactional client is installed if required, or use a bindings connection.
          at com.ibm.mq.connector.services.JCAExceptionBuilder.buildException(JCAExceptionBuilder.java:124)
          at com.ibm.mq.connector.services.JCAExceptionBuilder.buildException(JCAExceptionBuilder.java:86)
          at com.ibm.mq.connector.ResourceAdapterImpl.endpointActivation(ResourceAdapterImpl.java:417)
          at org.jboss.jca.core.rar.EndpointImpl.activate(EndpointImpl.java:164) [ironjacamar-core-impl-1.0.17.Final-redhat-1.jar:1.0.17.Final-redhat-1]
          at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.start(MessageDrivenComponent.java:178)
          ... 8 more