Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-9174

pooled-connection-factory doesn't allow to use "discovery-group" attribute as endpoint

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • 11.0.0.CR1
    • None
    • JMS
    • None
    • Hide

      Running EAP with attached config will reproduce the issue.

      Show
      Running EAP with attached config will reproduce the issue.

      Since EAP 7.1.0.ER3 we are not able to use discovery-group in pooled-connection-facotry to create remote JCA topology.

      When "discovery-group" attribute is used:
      <pooled-connection-factory name="activemq-ra" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" discovery-group="dg-group1" ha="false" min-large-message-size="102400" block-on-acknowledge="false" retry-interval="2000" retry-interval-multiplier="1.0" reconnect-attempts="-1" transaction="xa" min-pool-size="-1" max-pool-size="-1">

      Artemis RA initialization fails with following exception:

      14:00:40,098 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 77) MSC000001: Failed to start service jboss.raactivator.activemq-ra: org.jboss.msc.service.StartException in service jboss.raactivator.activemq-ra: WFLYJCA0046: Failed to start RA deployment [activemq-ra]
      	at org.jboss.as.connector.services.resourceadapters.deployment.AbstractResourceAdapterDeploymentService$2.run(AbstractResourceAdapterDeploymentService.java:332) [wildfly-connector-7.1.0.GA-redhat-4.jar:7.1.0.GA-redhat-4]
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_05]
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_05]
      	at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_05]
      	at org.jboss.threads.JBossThread.run(JBossThread.java:320) [jboss-threads-2.2.1.Final-redhat-1.jar:2.2.1.Final-redhat-1]
      Caused by: org.jboss.jca.deployers.common.DeployException: IJ020051: Unable to start org.apache.activemq.artemis.ra.ActiveMQResourceAdapter
      	at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.startContext(AbstractResourceAdapterDeployer.java:343) [ironjacamar-deployers-common-1.4.5.Final-redhat-1.jar:1.4.5.Final-redhat-1]
      	at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:2012) [ironjacamar-deployers-common-1.4.5.Final-redhat-1.jar:1.4.5.Final-redhat-1]
      	at org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator.doDeploy(ResourceAdapterActivatorService.java:171) [wildfly-connector-7.1.0.GA-redhat-4.jar:7.1.0.GA-redhat-4]
      	at org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService.start(ResourceAdapterActivatorService.java:115) [wildfly-connector-7.1.0.GA-redhat-4.jar:7.1.0.GA-redhat-4]
      	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) [jboss-msc-1.2.7.SP1-redhat-1.jar:1.2.7.SP1-redhat-1]
      	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) [jboss-msc-1.2.7.SP1-redhat-1.jar:1.2.7.SP1-redhat-1]
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_05]
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_05]
      	at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_05]
      Caused by: java.lang.IllegalArgumentException: must provide either TransportType or DiscoveryGroupAddress and DiscoveryGroupPort for ResourceAdapter Connection Factory
      	at org.apache.activemq.artemis.ra.ActiveMQResourceAdapter.newConnectionFactory(ActiveMQResourceAdapter.java:1761) [artemis-ra-1.5.5.006-redhat-1.jar:1.5.5.006-redhat-1]
      	at org.apache.activemq.artemis.ra.ActiveMQResourceAdapter.setup(ActiveMQResourceAdapter.java:1595) [artemis-ra-1.5.5.006-redhat-1.jar:1.5.5.006-redhat-1]
      	at org.apache.activemq.artemis.ra.ActiveMQResourceAdapter.start(ActiveMQResourceAdapter.java:246) [artemis-ra-1.5.5.006-redhat-1.jar:1.5.5.006-redhat-1]
      	at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.startContext(AbstractResourceAdapterDeployer.java:339) [ironjacamar-deployers-common-1.4.5.Final-redhat-1.jar:1.4.5.Final-redhat-1]
      	... 8 more
      
      14:00:40,104 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
          ("subsystem" => "messaging-activemq"),
          ("server" => "default"),
          ("pooled-connection-factory" => "activemq-ra")
      ]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.raactivator.activemq-ra" => "WFLYJCA0046: Failed to start RA deployment [activemq-ra]
          Caused by: org.jboss.jca.deployers.common.DeployException: IJ020051: Unable to start org.apache.activemq.artemis.ra.ActiveMQResourceAdapter
          Caused by: java.lang.IllegalArgumentException: must provide either TransportType or DiscoveryGroupAddress and DiscoveryGroupPort for ResourceAdapter Connection Factory"}}
      14:00:40,128 INFO  [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
      WFLYCTL0186:   Services which failed to start:      service jboss.raactivator.activemq-ra: WFLYJCA0046: Failed to start RA deployment [activemq-ra]
      

      Customer impact: Customers are not able to crate remote JCA connections in cluster.
      This is regression against 7.1.0.ER2

            jmesnil1@redhat.com Jeff Mesnil
            jmesnil1@redhat.com Jeff Mesnil
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: