JPA 2.1 code causing NPE when handling JTA transactions

Description

I ran the test case for on master, out of curiosity. JPA 2.1 related code is causing an NPE when looking for the JTA transaction. This doesn't happen on 4.1.8.

Not sure it's an actual bug on our end, but documenting just in case...

Logs:

https://gist.github.com/404fe6ddebce6fa90326

Activity

Show:

Christian Beikov January 15, 2025 at 1:45 PM

Closing since Bitronix was used for that test, which we removed as it's dead. I'll assume this is not an issue anymore.

Steve Ebersole October 28, 2015 at 3:26 AM

As part of verifying that this issue affects 5.0, please just set the "Affects version". Leave the "verify-affects-5.0" label and leave the issue in "Awaiting Response" status; these are critical for us to be able to track these verifications and triage them. Thanks.

Steve Ebersole October 27, 2015 at 7:16 PM

This bug report does not indicate that the reported issue affects version 5.x. Versions prior to 5.x are no longer maintained. It would be a great help to the Hibernate team and community for someone to verify that the reported issue still affects version 5.x. If so, please add the 5.x version that you verified with to the list of affected-versions and attach the (preferably SSCCE) test case you used to do the verification to the report; from there the issues will be looked at during our triage meetings.

For details, see http://in.relation.to/2015/10/27/great-jira-cleanup-2015/

Out of Date

Details

Assignee

Reporter

Labels

Affects versions

Priority

Created November 21, 2012 at 1:47 AM
Updated January 15, 2025 at 1:45 PM
Resolved January 15, 2025 at 1:45 PM