[
https://issues.apache.org/activemq/browse/AMQ-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58322#action_58322
]
Edan idzerda edited comment on AMQ-2656 at 3/19/10 3:10 AM:
------------------------------------------------------------
This version is based on the latest svn but adds an XAConnectionFactory to the
default list of factories, and sets the "xa" environment value manually for
that factory during creation. I was able to test the original patch
successfully, and this patch lets me lookup "XAConnectionFactory" via the JNDI
context which I believe will be required to easily integrate with webMethods.
Maybe it should be a regexp so any custom connection name with "XA" will get
the treatment? *shrug* I guess I think that at a minimum, a default
connection factory name like "XAConnectionFactory" should work without setting
environment variables. But I what do I know, seriously... ;)
was (Author: edan):
This version is based on the latest svn but adds an XAConnectionFactory to
the default list of factories, and sets the "xa" environment value manually for
that factory during creation.
> ActiveMQInitialConnectionFactory cannot return an XAConnectionFactory
> ---------------------------------------------------------------------
>
> Key: AMQ-2656
> URL: https://issues.apache.org/activemq/browse/AMQ-2656
> Project: ActiveMQ
> Issue Type: Bug
> Components: JMS client
> Affects Versions: 5.3.0
> Reporter: Edan idzerda
> Assignee: Gary Tully
> Fix For: 5.4.0
>
> Attachments: ActiveMQInitialContextFactory.java,
> ActiveMQInitialContextFactory.java
>
>
> ActiveMQInitialContextFactory cannot resolve the name "XAConnectionFactory"
> a la:
> INFO: JNDI API lookup failed: javax.naming.NameNotFoundException:
> XAConnectionFactory
> This prevents using the builtin JNDI service in an XA transaction context.
> I've created a simple patch to workaround this and discussed it on the
> mailing list:
> http://old.nabble.com/ActiveMQ%27s-JNDI-does-not-resolve-XAConnectionFactory-td27936255.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
