1 Reply Latest reply on Sep 5, 2017 10:17 AM by jason blackmore

    Startup problems WF 10 using websphere MQ resource adapter

    Mark McGregor Newbie

      Websphere MQ provides a resource adapter (wmq.jmsra.rar).   I have the latest for v8 (8.0.0.6).   But I can't get WF 10 to startup properly with the resource adapter and my ear.

       

      I deployed the rar using CLI.   The instance seems to start successfully when I don't provide an ear file with my instance.

       

      [2017-06-22 14:26:31,552] [INFO ] [MSC service thread 1-3(org.jboss.as.connector.deployers.RADeployer)] IJ020001: Required license terms for file:/home/chapp/product/ch_104251/jboss/standalone/tmp/...

      [2017-06-22 14:26:32,394] [WARN ] [MSC service thread 1-3(org.jboss.as.connector.deployers.RADeployer)] IJ020017: Invalid archive: file:/home/chapp/product/ch_104251/jboss/standalone/tmp/vfs/temp/...

      [2017-06-22 14:26:32,447] [INFO ] [MSC service thread 1-3(org.jboss.as.connector.deployers.RaXmlDeployer)] IJ020001: Required license terms for file:/home/chapp/product/ch_104251/jboss/standalone/tmp/vfs/temp/...

      [2017-06-22 14:26:32,479] [INFO ] [MSC service thread 1-3(org.jboss.as.connector.deployment)] WFLYJCA0007: Registered connection factory java:jboss/jms/DefaultJMSConnectionFactory

      [2017-06-22 14:26:32,480] [WARN ] [MSC service thread 1-3(org.jboss.as.connector.deployers.RaXmlDeployer)]

      IJ020016: Missing <recovery> element. XA recovery disabled for: java:jboss/jms/DefaultJMSConnectionFactory

      [2017-06-22 14:26:32,665] [INFO ] [MSC service thread 1-3(org.jboss.as.connector.deployment)] WFLYJCA0006: Registered admin object at java:jboss/jms/wmq/SYSTEMINFO

      [2017-06-22 14:26:32,776] [WARN ] [MSC service thread 1-3(org.jboss.as.connector.deployers.RaXmlDeployer)] IJ020017: Invalid archive: file:/home/chapp/product/ch_104251/jboss/standalone/tmp/vfs/temp/...

      [2017-06-22 14:26:33,250] [INFO ] [MSC service thread 1-3(org.jboss.as.connector.deployers.RaXmlDeployer)] IJ020002: Deployed: file:/home/chapp/product/ch_104251/jboss/standalone/tmp/vfs/temp/...

      [2017-06-22 14:26:33,254] [INFO ] [MSC service thread 1-1(org.jboss.as.connector.deployment)] WFLYJCA0002: Bound JCA ConnectionFactory [java:jboss/jms/DefaultJMSConnectionFactory]

      [2017-06-22 14:26:33,254] [INFO ] [MSC service thread 1-1(org.jboss.as.connector.deployment)] WFLYJCA0002: Bound JCA AdminObject [java:jboss/jms/wmq/SYSTEMINFO]

      [2017-06-22 14:26:33,307] [INFO ] [Controller Boot Thread(org.jboss.as.server)] WFLYSRV0010: Deployed "wmq.jmsra.rar" (runtime-name : "wmq.jmsra.rar")

       

       

      Not sure what the invalid archive messages at lines 2 and 7 mean -- perhaps those really are a problem.

       

      When I add my ear to the deployment directory I get this error on ear deployment:

       

      [2017-06-22 14:37:46,002] [ERROR] [MSC service thread 1-4(org.jboss.msc.service.fail)] MSC000001: Failed to start service jboss.deployment.subunit."copperhead-app-ear.ear"."copperhead-common-service.jar".component.SystemInfoListener.CREATE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."copperhead-app-ear.ear"."copperhead-common-service.jar".component.SystemInfoListener.CREATE: Failed to start service

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

              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

              at java.lang.Thread.run(Thread.java:745)

      Caused by: java.lang.IllegalStateException: WFLYEJB0383: No message listener of type javax.jms.MessageListener found in resource adapter wmq.jmsra.rar

              at org.jboss.as.ejb3.component.EJBUtilities.createActivationSpecs(EJBUtilities.java:102)

              at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentCreateService.createComponent(MessageDrivenComponentCreateService.java:103)

              at org.jboss.as.ee.component.BasicComponentCreateService.start(BasicComponentCreateService.java:90)

              at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentCreateService.start(MessageDrivenComponentCreateService.java:85)

              at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)

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

              ... 3 more

       

      I've looked over the ra.xml provided in the websphere rar, and there is a mapping for MessageListener.   And I find it unlikely that IBM doesn't bundle a MessageListener with their rar.

       

      <inbound-resourceadapter>

          <messageadapter>

              <messagelistener>

                    <messagelistener-type>

                           javax.jms.MessageListener

                    </messagelistener-type>

                    <activationspec>

                         <activationspec-class>

                                  com.ibm.mq.connector.inbound.ActivationSpecImpl

                         </activationspec-class>

       

      Any thoughts as to what might be up?

       

      I did notice that the websphere ra.xml uses connector xsd 1.7.   Does WF support the connect 1.7 xsd?     (Reason I ask is that the generic jms ra.xml provided with WF has 1.5).

       

      I've tried all sorts of things -- specifying the wmq class name in the MessageDriven annotation, setting up a module instead of a rar (it would not deploy, and didn't give any reason why, perhaps related to the invalid archive log messages).

       

      Not sure what other options exist.   generic jms?   Sadly the docs on this all seem to pre-date WF.

       

      Any insight would be greatly appreciated.