activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQ-2346) in managed environment, 2 connections/session, UserTransaction, transaction management gets confused
Date Thu, 03 Sep 2009 15:56:13 GMT

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

Gary Tully resolved AMQ-2346.
-----------------------------

    Resolution: Fixed

static back in place and made the removeCommand sync in transport connection to kill race
condition with starting a new connection with the same clientId.

revision: r811003

> in managed environment, 2 connections/session, UserTransaction, transaction management
gets confused
> ----------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-2346
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2346
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JCA Container
>    Affects Versions: 5.3.0
>            Reporter: David Jencks
>            Assignee: Gary Tully
>             Fix For: 5.3.0
>
>
> In geronimo we're seeing an intermittent tck problem that seems to relate to a situation
where there are:
> -- a BMT stateless session ejb
> -- two connections (I think these get shared to the same ManagedConnection)
> -- two sessions
> -- tx control through UT
> -- send a message in one tx
> -- receive message in a tx that is rolled back
> -- receive message in a tx that is committed
> In a public test case I'm seeing that the session proxies get confused about whether
there is an active transaction.  This doesn't happen all the time but with a few repititions
it happens consistently.
> See GERONIMO-4784

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