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] Commented: (AMQ-2656) ActiveMQInitialConnectionFactory cannot return an XAConnectionFactory
Date Fri, 19 Mar 2010 01:31:55 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58317#action_58317
] 

Edan idzerda commented on AMQ-2656:
-----------------------------------

At least from work, it took a while for the source code to show up in Crucible.  I saw it
before I left work, but I wasn't able to get it to work.  I'll try again tomorrow, but I get
ClassCastException trying to cast ActiveMQConnectionFactory to ActiveMQXAConnectionFactory.
 Maybe that should work since it's a subclass, but that error makes me doubtful :)  So far
I've only been successful with my patch which returns an ActiveMQXAConnectionFactory specifically.

>From within webMethods, I can set "other properties" which seem to be "jndi.properties."
  I tried adding "MyConnection" to my custom list of connectionFactoryNames, but I was unsuccessful
performing a context.lookup() on "MyConnection.xa=true" or "connection.MyConnection.xa=true"
...

If I can get your patch working, I still want to modify the DEFAULT_CONNECTION_FACTORY_NAMES
to include "XAConnectionFactory" to make it available as easily as the other standard JMS
types.  Thanks for your help on this :)

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