[
https://issues.apache.org/activemq/browse/SM-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Yu updated SM-1065:
------------------------
Attachment: SMX-1065-2.patch
Update the patch. Merged updates against latest 4.0 branch code.
----
For the transaction, actually, the jcaPoolConnectionFactory will enlist the
broker's xaResource into the transactionManager, if users provided the
transaction manager.
if users want to create a session, with the transactionManager, it will
populate xaResource in following code in XaConnectionPool:
session.setIgnoreClose(true);
transactionManager.getTransaction().registerSynchronization(new
Synchronization(session));
incrementReferenceCount();
transactionManager.getTransaction().enlistResource(createXaResource(session));
So, the jcaPoolConnectionFactory will know the this broker resource manager, if
it is RecoverableTransactionManager, it will loop the resources, and invoke:
recoverResourceManager(NamedXAResourceManager) accordingly.
> ActiveMQ integration
> --------------------
>
> Key: SM-1065
> URL: https://issues.apache.org/activemq/browse/SM-1065
> Project: ServiceMix
> Issue Type: New Feature
> Reporter: Guillaume Nodet
> Assignee: Jeff Yu
> Fix For: 4.0
>
> Attachments: SM-1065.patch, SMX-1065-2.patch
>
>
> ActiveMQ jars are already OSGified, but we may want to create a bundle that
> would create a broker by default and registering a pooled connection factory
> in OSGi maybe. That way, everyone could use the ConnectionFactory registered
> in OSGi.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
