[
https://issues.apache.org/activemq/browse/AMQ-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58519#action_58519
]
Gary Tully commented on AMQ-2670:
---------------------------------
Seems like the issue of of JCA XA recovery registration has come up in jboss
land, and it is correctly seen as something that should be handled under the
covers between JCA and the TransactionManager, but this has not been completed
yet. See: https://jira.jboss.org/jira/browse/JBJCA-39
There may be some way to workaround this with JMS apis in the short term, but
the real solution is to let the appserver work though registering the XA
resource from JCA with the underlying transaction services of the container.
> ClassCast Exception in JBoss when using XA
> -------------------------------------------
>
> Key: AMQ-2670
> URL: https://issues.apache.org/activemq/browse/AMQ-2670
> Project: ActiveMQ
> Issue Type: Bug
> Components: Connector
> Affects Versions: 5.3.0
> Environment: activemq-rar-5.3.0.rar deployed in jboss-5.1.0-GA
> Reporter: Edwin van der Elst
> Assignee: Gary Tully
> Fix For: 5.4.0
>
> Attachments: ActiveMQXAManagedConnectionFactory.java, ra.xml
>
>
> When deploying the rar under JBoss, the connectionfactory bound in de JNDI
> tree is always of type 'ActiveMQConnectionFactory'., while it should be
> ActiveMQXAConnectionFactory (which implements XAConnectionFactory).
> I attached a new class that creates the correct type of factory, and this can
> be configured in the ra.xml (also attached).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
