You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Forrest Xia (JIRA)" <ji...@apache.org> on 2012/06/10 10:04:42 UTC

[jira] [Resolved] (GERONIMO-4784) Problem with ActiveMQ, two connections/sessions, and UserTransaction

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

Forrest Xia resolved GERONIMO-4784.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 3.0

1. Seems the performance of activemq 5.4.x is a little bit slower and 5.3.x, especially when receiving message after a rollback, so set the second receive timeout to 2000 milliseconds.
2. Since G connector implemented transaction recovery, that will automatically recover the failed task next time, so the RollbackTest could fail when there are bad runs among several times call.
3. Adjust test counter smaller so that not timeout for failsafe plugin

Commit changes to 3.0-beta@1348545.
                
> Problem with ActiveMQ, two connections/sessions, and UserTransaction
> --------------------------------------------------------------------
>
>                 Key: GERONIMO-4784
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4784
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: ActiveMQ
>    Affects Versions: 2.2, 3.0
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 3.0, 2.2
>
>         Attachments: GERONIMO-4784-pom.patch, GERONIMO-4784-testng.patch, GERONIMO-4784-workaround.patch
>
>
> This is probably a problem in activemq with dealing with multiple connection handles to the same managed connection and XA transactions controlled by UserTransaction.  It may be causing intermittent tck failures.  In any case I think the test ought to work.
> Not sure how to reproduce this in AMQ standalone yet, so I'm adding a testsuite test to demonstrate the problem.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira