[
https://issues.apache.org/activemq/browse/AMQ-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58402#action_58402
]
Edan idzerda edited comment on AMQ-2656 at 3/23/10 8:15 PM:
------------------------------------------------------------
Why didn't you mention that in the first place!?!?! Oh... Because you did...
DOH!
Ok, that is working fine for both my Java client test and our webMethods
environment, even as far as verifying a transaction can be rolled back. I
still think XAConnectionFactory should be available without additional
configuration, for instance, just yesterday I had to remind a coworker to copy
the properties configuration after setting up a new system :)
But this is working and I don't want to be too pushy with my first reported
issue :) Thanks a lot for the help.
was (Author: edan):
Why did you mention that in the first place!?!?! Oh... Because you did...
DOH!
Ok, that is working fine for both my Java client test and our webMethods
environment, even as far as verifying a transaction can be rolled back. I
still think XAConnectionFactory should be available without additional
configuration, for instance, just yesterday I had to remind a coworker to copy
the properties configuration after setting up a new system :)
But this is working and I don't want to be too pushy with my first reported
issue :) Thanks a lot for the help.
> 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.
