tomee-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Gallimore (Jira)" <j...@apache.org>
Subject [jira] [Updated] (TOMEE-2561) Bad state in second connection to same datasource in same TX
Date Mon, 16 Sep 2019 19:32:02 GMT

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

Jonathan Gallimore updated TOMEE-2561:
--------------------------------------
    Fix Version/s:     (was: 8.0.0-Final)
                   8.0.1

> 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: 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.2#803003)

Mime
View raw message