You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tomee.apache.org by "Jonathan Gallimore (Jira)" <ji...@apache.org> on 2019/12/23 11:36:00 UTC

[jira] [Resolved] (TOMEE-2561) Bad state in second connection to same datasource in same TX

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

Jonathan Gallimore resolved TOMEE-2561.
---------------------------------------
    Fix Version/s:     (was: 8.0.2)
                   8.0.1
                   7.1.2
                   7.0.7
       Resolution: Fixed

> Bad state in second connection to same datasource in same TX
> ------------------------------------------------------------
>
>                 Key: TOMEE-2561
>                 URL: https://issues.apache.org/jira/browse/TOMEE-2561
>             Project: TomEE
>          Issue Type: Bug
>    Affects Versions: 7.0.6, 7.1.1, 8.0.0-M3
>            Reporter: Jonathan Gallimore
>            Assignee: Jonathan Gallimore
>            Priority: Major
>             Fix For: 7.0.7, 7.1.2, 8.0.1
>
>
> There's a case where, particularly if you're using XA, if you use a second connection to the same datasource in the same transaction, ManagedConnection will fetch the delegate transaction from the transaction registry, but the xaConnection and xaResource fields are dropped.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)