Uploaded image for project: 'WildFly WIP'
  1. WildFly WIP
  2. WFWIP-147

@JMSConnectionFactoryDefinition with property resourceAdapater to pooled-connection-factory defined in messaging-active subsystem does not work

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • JMS
    • None
    • Hide

      Steps to reproduce:

      git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
      cd eap-tests-hornetq/scripts/
      git checkout EAP7-1006
      
      groovy -DEAP_ZIP_URL=file:///<path_to_wf_zip> PrepareServers7.groovy
      export WORKSPACE=$PWD
      export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap
      export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap
      export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap
      export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap
      
      cd ../jboss-hornetq-testsuite/
      mvn clean test -Dtest=RemoteBrokerTestCase#testSubsystemCFDToRemoteBroker    -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.2.0.GA.CR1 | tee log
      
      Show
      Steps to reproduce: git clone git: //git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git cd eap-tests-hornetq/scripts/ git checkout EAP7-1006 groovy -DEAP_ZIP_URL=file: ///<path_to_wf_zip> PrepareServers7.groovy export WORKSPACE=$PWD export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap cd ../jboss-hornetq-testsuite/ mvn clean test -Dtest=RemoteBrokerTestCase#testSubsystemCFDToRemoteBroker -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.2.0.GA.CR1 | tee log

      If pooled-connection-factory is defined in messaging-active subsystem like:

                      <http-connector name="connector" socket-binding="messaging-socket-binding" endpoint="acceptor" server-name="default"/>
                       <pooled-connection-factory name="activemq-ra-remote" entries="java:/testJmsXA " connectors="connector" transaction="xa"/>     
      

      and deployment tries to use it to create @JMSConnectionFactoryDefinition like:

      @JMSConnectionFactoryDefinition(
              name="java:/jms/myRemoteJmsCf",
              resourceAdapter="activemq-ra-remote")
      

      then deploy fails with:

      13:21:18,284 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "mdb-activemq-1.0-SNAPSHOT.jar")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.raactivator.\"mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_java_/jms/myRemoteJmsCf\"" => "WFLYJCA0046: Failed to start RA deployment [mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_java_/jms/myRemoteJmsCf]
          Caused by: org.jboss.jca.deployers.common.DeployException: IJ020051: Unable to start org.wildfly.extension.messaging.activemq.ActiveMQResourceAdapter
          Caused by: java.lang.IllegalArgumentException: must provide either TransportType or DiscoveryGroupAddress and DiscoveryGroupPort for ResourceAdapter Connection Factory"}}
      13:21:18,295 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 48) WFLYSRV0010: Deployed "mdb-activemq-1.0-SNAPSHOT.jar" (runtime-name : "mdb-activemq-1.0-SNAPSHOT.jar")
      13:21:18,297 INFO  [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
      WFLYCTL0184:    New missing/unsatisfied dependencies:
            service jboss.connection-factory.reference-factory.jboss.naming.context.java.jms.myRemoteJmsCf (missing) dependents: [service jboss.naming.context.java.jms.myRemoteJmsCf] 
      WFLYCTL0186:   Services which failed to start:      service jboss.raactivator."mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_java_/jms/myRemoteJmsCf": WFLYJCA0046: Failed to start RA deployment [mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_java_/jms/myRemoteJmsCf]
      WFLYCTL0448: 5 additional services are down due to their dependencies being missing or failed
      

              ehugonne1@redhat.com Emmanuel Hugonnet
              mnovak1@redhat.com Miroslav Novak
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: