[
https://issues.apache.org/jira/browse/TOMEE-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Markus Jung reassigned TOMEE-4653:
----------------------------------
Assignee: Markus Jung
> EJB timer and container-managed transactions are left open after the call
> completes
> -----------------------------------------------------------------------------------
>
> Key: TOMEE-4653
> URL: https://issues.apache.org/jira/browse/TOMEE-4653
> Project: TomEE
> Issue Type: Bug
> Reporter: Markus Jung
> Assignee: Markus Jung
> Priority: Major
>
> When an EJB timer callback runs, TomEE logs "The EJB started a transaction
> but did not complete it." The same fault shows up in bean-managed and
> container-managed transaction tests across mandatory, required, requires-new,
> never, not-supported, and supports modes, and in schedule-based timer
> transaction tests. Rollback state also leaks between test methods.
> This points to a gap in how the transaction manager closes out transactions
> tied to timer and container-managed EJB calls: the manager starts the
> transaction but does not always complete it once the call returns.
> h2. Steps to reproduce / TCK reference
> Excluded in {{runner-webprofile/exclusions/enterprise-beans-30.txt}} in the
> apache/tomee-tck harness repo:
> * {{**/tx/bm/singleton/rw/*Test.java}}
> * {{**/tx/cm/singleton/rw/*Test.java}}
> * {{**/tx/cm/singleton/webrw/*Test.java}}
> * {{**/tx/cm/stateful/rw/*Test.java}}
> * {{**/tx/cm/stateful/webrw/*Test.java}}
> * {{**/tx/cm/stateless/rw/*Test.java}}
> * {{**/tx/cm/stateless/webrw/*Test.java}}
> Same fault in timer schedules, excluded in
> {{runner-webprofile/exclusions/enterprise-beans-32.txt}}:
> * {{**/timer/schedule/tx*/*Test.java}}
> Once fixed, remove the matching lines from both exclusion files and confirm
> the tests pass.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
