[
https://issues.apache.org/jira/browse/AMQ-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-4757.
-----------------------------
Resolution: Fixed
generic jms xa pool
- module: activemq-jms-pool
- package: org.apache.activemq.jms.pool package
existing impl remains
- module : activemq-pool
- package: org.apache.activemq.pool
> Provide a generic jms XA connection pool
> ----------------------------------------
>
> Key: AMQ-4757
> URL: https://issues.apache.org/jira/browse/AMQ-4757
> Project: ActiveMQ
> Issue Type: New Feature
> Components: JMS client
> Affects Versions: 5.8.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Labels: jms, pool, xa
> Fix For: 5.9.0
>
>
> When the jms bridge or camel is used with a third party jms provider the need
> for connection pooling and XA enlistment remains. The existing activemq-pool
> has hard dependencies on activemq so it cannot be used.
> the idea is to extract the AMQ deps and make activemq-jms-pool a dependent of
> activemq-pool so we can leverage the shared pool impl on both ends of a jms
> bridge or in camel.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
