[
https://jira.jboss.org/jira/browse/JBAS-7875?page=com.atlassian.jira.plug...
]
Carlo de Wolf commented on JBAS-7875:
-------------------------------------
rev 103466
Fixed in HornetQ 2.1.0.BETA1
ejb3/jbpapp3026 test is passing.
Auto creation of destinations for MDBs is broken
------------------------------------------------
Key: JBAS-7875
URL:
https://jira.jboss.org/jira/browse/JBAS-7875
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB3, JMS (HornetQ)
Reporter: jaikiran pai
Fix For: JBossAS-6.0.0.M3
The auto creation of destinations for MDBs is broken in AS trunk with HornetQ. The
org.jboss.as.integration.hornetq.deployers.DestinationFactoryDeployerPlugin responsible
for creating the destination has multiple issues:
1) It uses the "destination" activation config property as the destination
*name* and then creates a jndi name for that destination. This is incorrect because the
"destination" activation config property itself is the jndi name.
2) This org.jboss.as.integration.hornetq.deployers.DestinationFactoryDeployerPlugin
along with the CreateDestinationDeployer creates a JMSConfiguration as an attachment to
the deployment unit. If there are more than one MDBs which require creation of
destinations, then this deployer ends up using the same attachment name for both the
attachment names, ending up the "last one is the winner" scenario.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira