[jboss-jira] [JBoss JIRA] (AS7-2083) Exception when specifying discovery-group-ref under connection-factory / pooled-connection-factory in messaging subsystem
Evangelos Parchas (Commented) (JIRA)
jira-events at lists.jboss.org
Thu Nov 3 10:58:45 EDT 2011
[ https://issues.jboss.org/browse/AS7-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639728#comment-12639728 ]
Evangelos Parchas commented on AS7-2083:
----------------------------------------
Any news regarding which version is this planned to be resolved?
> Exception when specifying discovery-group-ref under connection-factory / pooled-connection-factory in messaging subsystem
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-2083
> URL: https://issues.jboss.org/browse/AS7-2083
> Project: Application Server 7
> Issue Type: Bug
> Components: JMS
> Affects Versions: 7.0.1.Final, 7.0.2.Final
> Environment: Ubuntu 11.04 64bit, Java 1.6
> Reporter: Evangelos Parchas
> Assignee: Clebert Suconic
>
> An error is produced when specifying a "discovery-group-ref" under either a "connection-factory" or "pooled-connection-factory" in the messaging subsystem configuration:
> {code}
> <connection-factory name="RemoteConnectionFactory">
> <discovery-group-ref discovery-group-name="dg-group1"/>
> <entries>
> <entry name="java:/RemoteConnectionFactory"/>
> </entries>
> </connection-factory>
> {code}
> {code}
> <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>
> {code}
> The exception present in the server.log is:
> {code}
> 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
> {code}
> 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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list