[ https://issues.apache.org/activemq/browse/AMQ-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58312#action_58312 ]
Gary Tully commented on AMQ-2656: --------------------------------- check out the subversion commits tag to see the changes. It may not be enough for you if you cannot augment the environment to add the xa=true property. there is also a property for the connectionFactoryNames where you can provide the list of names you will expect. This overrides the DEFAULT_CONNECTION_FACTORY_NAMES > 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.