[
https://issues.apache.org/jira/browse/AMQ-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986433#action_12986433
]
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 environment?
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: https://issues.apache.org/jira/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.
