You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2011/01/28 21:22:44 UTC

[jira] Reopened: (AMQ-2656) ActiveMQInitialConnectionFactory cannot return an XAConnectionFactory

     [ https://issues.apache.org/jira/browse/AMQ-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully reopened AMQ-2656:
-----------------------------


opening so we don't forget to add a hard coded xa factory name.

> 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.