1 2 3 Previous Next 30 Replies Latest reply: Sep 29, 2011 10:55 AM by dstockdreher Go to original post RSS
      • 15. Re: Creating resources for a resource adapter
        dstockdreher Newbie

        Pulled down 7.0.1, and it looks like the RA is getting set up and deployed correctly now

         

        INFO  [org.jboss.as.connector.metadata.deployment.ResourceAdapterXmlDeploymentService$AS7RaXmlDeployer] (MSC service thread 1-2) Registered connection factory java:jboss/eis/MQCF

         

        However, when I then try to deploy an app with an MDB with

          @ResourceAdapter(value = "wmq.jmsra.rar")

         

        I'm getting the following. 

         

        Caused by: java.lang.IllegalStateException: No resource-adapter has been specified for MessageDrivenComponent MqServiceMessageBean

            at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.start(MessageDrivenComponent.java:171)

         

        Do I have some sort of mismatch in the ra config in standalone.xml?

         

         


        <subsystem xmlns="urn:jboss:domain:resource-adapters:1.0">

        <resource-adapters>

        <resource-adapter>

        <archive>

        wmq.jmsra.rar

        </archive>

        <config-property name="port">

        1414

        </config-property>

        <config-property name="hostName">

        hostname

        </config-property>

        <config-property name="channel">

        SVRCONN.CHAN

        </config-property>

        <config-property name="transportType">

        CLIENT

        </config-property>

        <config-property name="queueManager">

        QMNAME

        </config-property>

        <connection-definitions>

        <connection-definition class-name="com.ibm.mq.connector.outbound.ManagedConnectionFactoryImpl" jndi-name="java:jboss/eis/MQCF" enabled="true" use-java-context="true" pool-name="mqConnectionFactory" use-ccm="true">

        <pool>

        <min-pool-size>

        1

        </min-pool-size>

        <max-pool-size>

        10

        </max-pool-size>

        <prefill>

        false

        </prefill>

        <use-strict-min>

        false

        </use-strict-min>

        </pool>

        <security>

        <application>

        true

        </application>

        </security>

        </connection-definition>

        </connection-definitions>

        </resource-adapter>

        </resource-adapters>

        </subsystem>
        • 16. Re: Creating resources for a resource adapter
          jaikiran pai Master

          I don't see anything wrong in that configuration or the @ResourceAdapter value. The annotation is @org.jboss.ejb3.annotation.ResourceAdapter right?

          Until, I figure out what's wrong, can you try editing the ejb3 subsystem configuration in your standalone-preview.xml to use wmq.jmsra.rar as the default resource adapter for MDBs:

          <subsystem xmlns="urn:jboss:domain:ejb3:1.1" >
              <!-- Default MDB configurations -->
              <mdb>
                  <resource-adapter-ref resource-adapter-name="wmq.jmsra.rar"/>
          ...
          

           

          If that doesn't work, the other thing you could try is, start the server first with the RA configurations and .rar deployed but without the MDB. Once the server starts successfully, then try deploying the MDB jar. See if that works. I think I know what's going on, but I find it surprising that an API isn't throwing an exception which I would have expected to be thrown.

          • 17. Re: Creating resources for a resource adapter
            dstockdreher Newbie

            I had tried to start the server first with just the RA and then deploy the app.  Both before and after adding the default resource adapter.

             

            Either case I still get the same error.

             

            Caused by: java.lang.IllegalStateException: No resource-adapter has been specified for MessageDrivenComponent MqServiceMessageBean

                at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.start(MessageDrivenComponent.java:171)

            • 18. Re: Creating resources for a resource adapter
              jaikiran pai Master

              Let me see how I can reproduce this.

              • 19. Re: Creating resources for a resource adapter
                dstockdreher Newbie

                Without  @ResourceAdapter and without the default mdb config in standalone.xml  it winds up looking for the hornetq-ra which is the default.

                 

                Adding in only the default config produces the same error above with or without the @ResourceAdapter on the bean.

                 

                If I remove the resource-adapter config from standalone.xml I get NPE's (didn't expect that attempt to work anyway, just wanted to be thorough)

                • 20. Re: Creating resources for a resource adapter
                  jaikiran pai Master

                  Can you please attach the server.log when you do the following:

                   

                  1) Start the server with the RA config and the .rar in the standalone/deployments.

                  2) Wait for the server to start and the .rar to be deployed

                  3) Now place your MDB jar in the standalone/deployments and see it being picked up for deployment

                   

                  Please attach that server.log (along with the exception stacktrace). I am trying to figure out why that case doesn't work, assuming I have narrowed it down correctly to what I think is a service dependency issue.

                  • 21. Re: Creating resources for a resource adapter
                    jaikiran pai Master

                    I just reproduced this locally, let me see what's going on.

                    • 22. Re: Creating resources for a resource adapter
                      dstockdreher Newbie

                      Server log with  default and resource adapter defined in standalone.xml  only the rar deployed ( no app)

                       

                      12:07:23,752 INFO  [org.jboss.modules] JBoss Modules version 1.0.1.GA

                      12:07:24,033 INFO  [org.jboss.msc] JBoss MSC version 1.0.0.GA

                      12:07:24,080 INFO  [org.jboss.as] JBoss AS 7.0.1.Final "Zap" starting

                      12:07:25,018 WARN  [org.jboss.as] No security realm defined for native management service, all access will be unrestricted.

                      12:07:25,096 INFO  [org.jboss.as] creating http management service using network interface (management) port (9990)

                      12:07:25,096 WARN  [org.jboss.as] No security realm defined for http management service, all access will be unrestricted.

                      12:07:25,096 INFO  [org.jboss.as.webservices] Activating WebServices Extension

                      12:07:25,127 INFO  [org.jboss.as.logging] Removing bootstrap log handlers

                      12:07:25,143 INFO  [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)

                      12:07:25,143 INFO  [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2)

                      12:07:25,158 INFO  [org.jboss.as.clustering.infinispan.subsystem] (Controller Boot Thread) Activating Infinispan subsystem.

                      12:07:25,268 INFO  [org.jboss.as.naming] (Controller Boot Thread) Activating Naming Subsystem

                      12:07:25,283 INFO  [org.jboss.as.osgi] (Controller Boot Thread) Activating OSGi Subsystem

                      12:07:25,283 INFO  [org.jboss.as.naming] (MSC service thread 1-2) Starting Naming Service

                      12:07:25,315 INFO  [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem

                      12:07:25,315 INFO  [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 3.2.0.Beta2

                      12:07:25,330 INFO  [org.xnio] (MSC service thread 1-1) XNIO Version 3.0.0.Beta3

                      12:07:25,362 INFO  [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.0.0.Beta3

                      12:07:25,440 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-4) JBoss Web Services - Stack CXF Server 4.0.0.Beta3

                      12:07:25,783 INFO  [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-1) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jdk1.6.0_26\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:/Program Files/Java/jre6/bin/client;C:/Program Files/Java/jre6/bin;C:/Program Files/Java/jre6/lib/i386;C:\Program Files\Apache Software Foundation\apache-maven-3.0.3\bin;C:\Program Files\IBM\WebSphere MQ\Java\lib;C:\Hyperion\essbase\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\PROGRA~1\Java\jdk1.6.0_26\bin;C:\epcdev\jboss-as-7.0.1.Final\bin;C:\PROGRA~1\IBM\CLIENT~1;C:\PROGRA~1\IBM\CLIENT~1\Shared;C:\PROGRA~1\IBM\CLIENT~1\Emulator;C:\Program Files\Common Files\Roxio Shared\DLLShared\;C:\Program Files\Common Files\Roxio Shared\10.0\DLLShared\;C:\Program Files\RSA Security\RSA SecurID Software Token\;C:\FPW26A;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\Program Files\Microsoft SQL Server\80\Tools\BINN;C:\Program Files\MySQL\MySQL Server 5.5\bin;C:\Program Files\IBM\WebSphere MQ\bin;C:\Program Files\IBM\WebSphere MQ\tools\c\samples\bin;C:\Documents and Settings\drew.stockdreher;;.

                      12:07:25,908 INFO  [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem

                      12:07:26,080 INFO  [org.jboss.as.remoting] (MSC service thread 1-4) Listening on /127.0.0.1:9999

                      12:07:26,268 INFO  [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-4) Starting remote JMX connector

                      12:07:26,315 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080

                      12:07:26,502 INFO  [org.jboss.as.connector] (MSC service thread 1-1) Starting JCA Subsystem (JBoss IronJacamar 1.0.3.Final)

                      12:07:26,533 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) Bound data source [java:jboss/datasources/ExampleDS]

                      12:07:26,549 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) Bound data source [jdbc/epcfedb]

                      12:07:26,565 INFO  [org.jboss.as.deployment] (MSC service thread 1-1) Started FileSystemDeploymentService for directory C:\epcdev\jboss-as-7.0.1.Final\standalone\deployments

                      12:07:26,596 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "wmq.jmsra.rar"

                      12:07:27,487 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.mqjms.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.mq.jms.admin.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,487 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.msg.client.jms.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.msg.client.jms.internal.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,487 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.msg.client.provider.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.msg.client.jms.internal.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,487 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.mq.jmqi.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.msg.client.wmq.factories.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,487 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.mq.jmqi.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.msg.client.wmq.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,487 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.mq.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.mq.pcf.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,487 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.mq.headers.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.mq.pcf.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,487 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.msg.client.jms.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.mqjms.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,487 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.msg.client.commonservices.j2se.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.mqjms.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,487 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.msg.client.wmq.common.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.mqjms.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,487 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.msg.client.wmq.factories.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.mqjms.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,487 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.msg.client.wmq.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.mqjms.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,487 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.msg.client.wmq.v6.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.mqjms.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,487 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.mq.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.mqjms.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,487 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry ldap.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.mqjms.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,487 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jndi.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.mqjms.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,487 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry fscontext.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.mqjms.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,487 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry providerutil.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.mqjms.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,487 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.mq.jms.admin.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.mqjms.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,487 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jms.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.msg.client.jms.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,487 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.msg.client.jms.internal.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.msg.client.jms.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,487 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.msg.client.commonservices.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.msg.client.jms.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,487 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.msg.client.provider.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.msg.client.jms.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,487 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.msg.client.jms.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.msg.client.matchspace.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,502 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.mq.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.mq.headers.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,502 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry rmm.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.msg.client.wmq.v6.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,502 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry CL3Export.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.msg.client.wmq.v6.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,502 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry CL3Nonexport.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.msg.client.wmq.v6.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,502 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry dhbcore.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.msg.client.wmq.v6.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,502 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.mq.headers.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.mq.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,502 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.mq.pcf.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.mq.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,502 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.mq.jmqi.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.mq.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,502 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry connector.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.mq.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,502 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.mq.commonservices.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.mq.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,502 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry dhbcore.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/dhbcore.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,502 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.mq.jmqi.local.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.mq.jmqi.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,502 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.mq.jmqi.remote.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.mq.jmqi.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,502 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.mq.jmqi.system.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.mq.jmqi.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,502 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jta.jar in "/C:/epcdev/jboss-as-7.0.1.Final/bin/content/wmq.jmsra.rar/com.ibm.mq.jmqi.jar"  does not point to a valid jar for a Class-Path reference.

                      12:07:27,580 INFO  [org.jboss.as.jpa] (MSC service thread 1-1) added javax.persistence.api dependency to wmq.jmsra.rar

                      12:07:27,955 INFO  [org.jboss.as.connector.metadata.deployment.ResourceAdapterDeploymentService$AS7RaDeployer] (MSC service thread 1-2) IJ020001: Required license terms for file:/C:/epcdev/jboss-as-7.0.1.Final/standalone/tmp/vfs/tempe0c2784c72d3680b/wmq.jmsra.rar-4ba9463fb9216835/contents/

                      12:07:28,346 INFO  [org.jboss.as.connector.metadata.deployment.ResourceAdapterXmlDeploymentService$AS7RaXmlDeployer] (MSC service thread 1-2) IJ020001: Required license terms for file:/C:/epcdev/jboss-as-7.0.1.Final/standalone/tmp/vfs/tempe0c2784c72d3680b/wmq.jmsra.rar-4ba9463fb9216835/contents/

                      12:07:28,362 INFO  [org.jboss.as.connector.metadata.deployment.ResourceAdapterXmlDeploymentService$AS7RaXmlDeployer] (MSC service thread 1-2) Registered connection factory java:jboss/eis/ccdbMQCF

                      12:07:28,377 INFO  [stdout] (MSC service thread 1-2) MQJCA4005:Distributed transactions are not available in client mode.

                       

                      12:07:28,393 INFO  [org.jboss.as.connector.metadata.deployment.ResourceAdapterXmlDeploymentService$AS7RaXmlDeployer] (MSC service thread 1-2) IJ020002: Deployed: file:/C:/epcdev/jboss-as-7.0.1.Final/standalone/tmp/vfs/tempe0c2784c72d3680b/wmq.jmsra.rar-4ba9463fb9216835/contents/

                      12:07:28,393 INFO  [org.jboss.as] (MSC service thread 1-2) JBoss AS 7.0.1.Final "Zap" started in 4922ms - Started 120 of 177 services (57 services are passive or on-demand)

                      12:07:28,502 INFO  [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployed "wmq.jmsra.rar"

                       

                       

                       

                      Server log after deploying the app containing the MDB

                       

                      12:09:28,599 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) Starting deployment of "epc-fe.war"

                      12:09:36,443 INFO  [org.jboss.jpa] (MSC service thread 1-2) read persistence.xml for epcjpa2

                      12:09:36,443 INFO  [org.jboss.as.jpa] (MSC service thread 1-1) added javax.persistence.api, javaee.api, org.jboss.as.jpa, org.javassist dependencies to epc-fe.war

                      12:09:36,443 INFO  [org.jboss.as.jpa] (MSC service thread 1-1) added (default provider) org.hibernate dependency to application deployment (since 1 PU(s) didn't specify jboss.as.jpa.providerModule)

                      12:09:36,443 INFO  [org.jboss.as.jpa] (MSC service thread 1-1) added org.hibernate dependency to application deployment

                      12:09:36,552 INFO  [org.jboss.weld] (MSC service thread 1-4) Processing CDI deployment: epc-fe.war

                      12:09:36,568 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named XXXEJB in deployment unit deployment "epc-fe.war" are as follows:

                       

                        ......  EJB deployments

                       

                      12:09:36,959 INFO  [org.jboss.weld] (MSC service thread 1-4) Starting Services for CDI deployment: epc-fe.war

                      12:09:36,990 INFO  [org.jboss.weld.Version] (MSC service thread 1-4) WELD-000900 1.1.2 (Final)

                      12:09:37,021 WARN  [org.jboss.ejb3] (MSC service thread 1-3) ActivationConfigProperty "messagingType" will be ignored since it is not allowed by resource adapter: wmq.jmsra

                      12:09:37,021 INFO  [org.jboss.jpa] (MSC service thread 1-1) starting Persistence Unit Service 'epc-fe.war#epcjpa2'

                      12:09:37,037 INFO  [org.jboss.weld] (MSC service thread 1-2) Starting weld service

                      12:09:37,162 INFO  [org.hibernate.annotations.common.Version] (MSC service thread 1-1) Hibernate Commons Annotations 3.2.0.Final

                      12:09:37,162 INFO  [org.hibernate.cfg.Environment] (MSC service thread 1-1) HHH00412:Hibernate [WORKING]

                      12:09:37,162 INFO  [org.hibernate.cfg.Environment] (MSC service thread 1-1) HHH00206:hibernate.properties not found

                      12:09:37,162 INFO  [org.hibernate.cfg.Environment] (MSC service thread 1-1) HHH00021:Bytecode provider name : javassist

                      12:09:37,177 INFO  [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-1) HHH00204:Processing PersistenceUnitInfo [

                          name: epcjpa2

                          ...]

                      ..... hibernate warnings.


                      12:09:37,615 INFO  [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] (MSC service thread 1-1) HHH00130:Instantiating explicit connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider

                      12:09:37,677 INFO  [org.hibernate.dialect.Dialect] (MSC service thread 1-1) HHH00400:Using dialect: org.hibernate.dialect.MySQL5Dialect

                      12:09:37,693 INFO  [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] (MSC service thread 1-1) HHH00268:Transaction strategy: org.hibernate.engine.transaction.internal.jta.CMTTransactionFactory

                      12:09:37,693 INFO  [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (MSC service thread 1-1) HHH00397:Using ASTQueryTranslatorFactory

                      12:09:37,724 INFO  [org.hibernate.validator.util.Version] (MSC service thread 1-1) Hibernate Validator 4.2.0.Final

                      12:09:38,474 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."epc-fe.war".component.MqServiceMessageBean.START: org.jboss.msc.service.StartException in service jboss.deployment.unit."epc-fe.war".component.MqServiceMessageBean.START: Failed to start service

                          at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1786)

                          at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)

                          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26]

                          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26]

                          at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]

                      Caused by: java.lang.IllegalStateException: No resource-adapter has been specified for MessageDrivenComponent MqServiceMessageBean

                          at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.start(MessageDrivenComponent.java:171)

                          at org.jboss.as.ee.component.ComponentStartService.start(ComponentStartService.java:44)

                          at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)

                          ... 4 more

                       

                      12:09:38,490 INFO  [org.apache.catalina.core.StandardContext] (MSC service thread 1-4) The listener "com.sun.faces.config.ConfigureListener" is already configured for this context. The duplicate definition has been ignored.

                      12:09:38,568 INFO  [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-4) Initializing Mojarra 2.0.4 (FCS b09-jbossorg-4) for context '/epc-fe'

                      12:09:40,412 INFO  [org.primefaces.webapp.PostConstructApplicationEventListener] (MSC service thread 1-4) Running on PrimeFaces 3.0.M2

                      12:09:40,521 INFO  [org.jboss.web] (MSC service thread 1-4) registering web context: /epc-fe

                      12:09:40,521 INFO  [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployment of "epc-fe.war" was rolled back with failure message {"Failed services" => {"jboss.deployment.unit.\"epc-fe.war\".component.MqServiceMessageBean.START" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"epc-fe.war\".component.MqServiceMessageBean.START: Failed to start service"}}

                      12:09:40,521 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 2) Service status report

                        Services which failed to start:

                            service jboss.deployment.unit."epc-fe.war".component.MqServiceMessageBean.START: org.jboss.msc.service.StartException in service jboss.deployment.unit."epc-fe.war".component.MqServiceMessageBean.START: Failed to start service

                       

                      12:09:40,521 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads - 1) {"Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"Failed services" => {"jboss.deployment.unit.\"epc-fe.war\".component.MqServiceMessageBean.START" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"epc-fe.war\".component.MqServiceMessageBean.START: Failed to start service"}}}}

                      12:09:40,568 INFO  [org.jboss.jpa] (MSC service thread 1-2) stopping Persistence Unit Service 'epc-fe.war#epcjpa2'

                      12:09:40,568 INFO  [org.jboss.weld] (MSC service thread 1-2) Stopping weld service

                      12:09:41,115 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) Stopped deployment epc-fe.war in 589ms

                       

                      Let me know what else you might need.   (also removed the messagingType from the activationconfig in the MDB and it made no difference)

                      • 24. Re: Creating resources for a resource adapter
                        jaikiran pai Master

                        We've identified a bug and working towards a fix. We'll let you know soon.

                        • 25. Re: Creating resources for a resource adapter
                          dstockdreher Newbie

                          Is there a JIRA created for tracking purposes?

                          • 26. Re: Creating resources for a resource adapter
                            jaikiran pai Master

                            Yes, they are linked to this thread (top right corner, "Related issues" widget). Anyway, these are the issues:

                             

                            https://issues.jboss.org/browse/AS7-1580 (the one you are running into)

                            https://issues.jboss.org/browse/AS7-1568 (a related one)

                            • 27. Re: Creating resources for a resource adapter
                              jaikiran pai Master

                              We believe that with our latest commits, the latest AS7 upstream should have all the neccessary fixes to allow you to get past these issues. Please try the latest nightly build and let us know how it goes.

                              • 28. Re: Creating resources for a resource adapter
                                dstockdreher Newbie

                                We pulled down the nightly build, but are still having issues with getting the RA to install correctly.

                                 

                                Currently I'm gettting the following Stacktrace on server startup.

                                 

                                10:24:58,945 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.raxml."wmq.jmsra": org.jboss.msc.service.StartException in service jboss.raxml."wmq.jmsra": org.jboss.msc.service.StartException in anonymous service: Failed to start RA deployment [wmq.jmsra]

                                    at org.jboss.as.connector.metadata.deployment.ResourceAdapterXmlDeploymentService.start(ResourceAdapterXmlDeploymentService.java:119)

                                    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]

                                    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]

                                    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26]

                                    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26]

                                    at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]

                                Caused by: org.jboss.msc.service.StartException in anonymous service: Failed to start RA deployment [wmq.jmsra]

                                    at org.jboss.as.connector.metadata.deployment.ResourceAdapterXmlDeploymentService.start(ResourceAdapterXmlDeploymentService.java:105)

                                    ... 5 more

                                Caused by: org.jboss.jca.deployers.common.DeployException: IJ020060: Unable to inject: com.ibm.mq.connector.ResourceAdapterImpl property: port value: 21414

                                    at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:983)

                                    at org.jboss.as.connector.metadata.deployment.ResourceAdapterXmlDeploymentService$AS7RaXmlDeployer.doDeploy(ResourceAdapterXmlDeploymentService.java:153)

                                    at org.jboss.as.connector.metadata.deployment.ResourceAdapterXmlDeploymentService.start(ResourceAdapterXmlDeploymentService.java:103)

                                    ... 5 more

                                 

                                 

                                My setup is the following.   -  Nightly Build of AS 7  (7.1.0 alpha)

                                 

                                In my standalone.xml I have the following 

                                 

                                <subsystem xmlns="urn:jboss:domain:resource-adapters:1.0">

                                            <resource-adapters>

                                                <resource-adapter>

                                                    <archive>

                                                        wmq.jmsra.rar

                                                    </archive>

                                                    <config-property name="port">

                                                        21414

                                                    </config-property>

                                                    <config-property name="hostName">

                                                        89HFZK1.corp.mycomp.com

                                                    </config-property>

                                                    <config-property name="channel">

                                                        TO_QM_89HFZK1

                                                    </config-property>

                                                    <config-property name="transportType">

                                                        CLIENT

                                                    </config-property>

                                                    <config-property name="queueManager">

                                                        QM_89HFZK1

                                                    </config-property>

                                                    <connection-definitions>

                                                        <connection-definition class-name="com.ibm.mq.connector.outbound.ManagedConnectionFactoryImpl" jndi-name="java:jboss/eis/ccdbMQCF" pool-name="ccdbConnectionFactory">

                                                            <pool>

                                                                <min-pool-size>

                                                                    1

                                                                </min-pool-size>

                                                                <max-pool-size>

                                                                    10

                                                                </max-pool-size>

                                                            </pool>

                                                            <security>

                                                                <application>

                                                                    true

                                                                </application>

                                                            </security>

                                                        </connection-definition>

                                                    </connection-definitions>

                                                </resource-adapter>

                                            </resource-adapters>

                                        </subsystem>

                                 

                                 

                                And I have put the wmq.jmsra.rar in the deployments folder.  

                                 

                                Could you maybe provide the configuration details for the setup used to verify the fix while it was being committed for comparison purposes?

                                • 29. Re: Creating resources for a resource adapter
                                  Jesper Pedersen Master

                                  config-property's for the MCF needs to go under the <connection-definition> element.