activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <>
Subject [jira] Commented: (AMQ-2656) ActiveMQInitialConnectionFactory cannot return an XAConnectionFactory
Date Tue, 25 Jan 2011 15:30:43 GMT


Gary Tully commented on AMQ-2656:

@peter, thanks for closing the loop on this with the feeback.
So in 2.ii or 3.i - there is no possibility to specify an additional property for the jndi
not good. 

So either we have a hardcoded xaconnection factory, Edan's fix, or the 'xa=true' jndi env
property needs to be embedded in the 2.ii external provider url, like tcp://localhost:61616?jndi.xa=true

> 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