activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edan idzerda (JIRA)" <>
Subject [jira] Commented: (AMQ-2656) ActiveMQInitialConnectionFactory cannot return an XAConnectionFactory
Date Fri, 19 Mar 2010 15:47:45 GMT


Edan idzerda commented on AMQ-2656:

Thanks for the pointers on the properties.  I was able to just have a line with "xa=true"
in both my for my standalone java client test and the "Other Properties" in
webMethods and create an "XA" transaction by just looking up "ConnectionFactory."  It seems
to apply to all ConnectionFactory lookups, though, so my standalone java client gets an exception
when sending a message:

javax.jms.JMSException: Session's XAResource has not been enlisted in a distributed transaction.

I assume there is no way to limit the xa=true property to a particular connection factory
lookup with this method.  (If I use your snippet above a lookup of "ConnectionFactory" fails,
for instance.)  It seems less desirable to me to be forced into creating separate processes
or JNDI Providers in webMethods to do XA or not.  But I can work with the patch you have submitted
for 5.4.0, as opposed to current.  Once we've had a chance to test out the current patch in
webMethods more, perhaps we will see if it is a big of a pain or not.  

I'm tempted to keep my patch locally, as it strikes me as much easier to remember "just look
up XAConnectionFactory if that's what you need" as opposed to configuring the environment.
 OTOH, it may be harder to remember to keep my local patch when we upgrade someday :)  Thanks

> ActiveMQInitialConnectionFactory cannot return an XAConnectionFactory
> ---------------------------------------------------------------------
>                 Key: AMQ-2656
>                 URL:
>             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 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:

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message