activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edan idzerda (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AMQ-2656) ActiveMQInitialConnectionFactory cannot return an XAConnectionFactory
Date Fri, 19 Mar 2010 03:05:45 GMT

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

Edan idzerda updated AMQ-2656:
------------------------------

    Attachment: ActiveMQInitialContextFactory.java

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.


Mime
View raw message