Uploaded image for project: 'Application Server 7'
  1. Application Server 7
  2. AS7-2083

Exception when specifying discovery-group-ref under connection-factory / pooled-connection-factory in messaging subsystem

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 7.1.0.Final
    • 7.0.1.Final, 7.0.2.Final
    • JMS
    • None
    • Hide

      Configure a discovery group for your hornetq cluster.
      Reference the discovery group in the connection-factory as allowed by the messaging xsd.
      Start server and inspect the logs.

      Show
      Configure a discovery group for your hornetq cluster. Reference the discovery group in the connection-factory as allowed by the messaging xsd. Start server and inspect the logs.

    Description

      An error is produced when specifying a "discovery-group-ref" under either a "connection-factory" or "pooled-connection-factory" in the messaging subsystem configuration:

      <connection-factory name="RemoteConnectionFactory">
          <discovery-group-ref discovery-group-name="dg-group1"/>
          <entries>
              <entry name="java:/RemoteConnectionFactory"/>
          </entries>
      </connection-factory>
      
      <pooled-connection-factory name="RemoteXAConnectionFactory">
          <discovery-group-ref discovery-group-name="dg-group1"/>
          <entries>
              <entry name="java:/RemoteXAConnectionFactory"/>
          </entries>
          <transaction mode="xa"/>
      </pooled-connection-factory>
      

      The exception present in the server.log is:

      14:40:45,466 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-16) MSC00001: Failed to start service jboss.raactivator: org.jboss.msc.service.St
      artException in service jboss.raactivator: Failed to activate resource adapter RemoteXAConnectionFactory
              at org.jboss.as.connector.services.ResourceAdapterActivatorService.start(ResourceAdapterActivatorService.java:98)
              at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
              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: org.jboss.jca.deployers.common.DeployException: Deployment org.hornetq.ra.HornetQResourceAdapter failed
              at org.jboss.as.connector.metadata.deployment.AbstractResourceAdapterDeploymentService$AbstractAS7RaDeployer.initAndInject(AbstractResourceAdap
      terDeploymentService.java:382)
              at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:900)
              at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:825)
              at org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator.doDeploy(ResourceAdapterActivatorService.java:140)
              at org.jboss.as.connector.services.ResourceAdapterActivatorService.start(ResourceAdapterActivatorService.java:93)
              ... 5 more
      Caused by: java.lang.NoSuchMethodException: org.hornetq.ra.HornetQResourceAdapter.setDiscoveryGroupName(java.lang.String)
              at java.lang.Class.getMethod(Class.java:1605) [:1.6.0_26]
              at org.jboss.as.connector.util.Injection.inject(Injection.java:149)
              at org.jboss.as.connector.metadata.deployment.AbstractResourceAdapterDeploymentService$AbstractAS7RaDeployer.initAndInject(AbstractResourceAdap
      terDeploymentService.java:374)
              ... 9 more
      

      Looking at HornetQResourceAdapter, it does not provide a method called "setDiscoveryGroupName" but a "setDiscoveryAddress" which bears the javadoc that it corresponds to the discovery group name.

      This prevents successful configuration of the messaging subsystem for clustered environments

      Attachments

        Activity

          People

            rh-ee-ataylor Andy Taylor
            eparchas Evangelos Parchas (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: