Bug 847231 - "Could not commit session or rollback" exception is thrown when session with Spring Transaction Manager is being disposed
Summary: "Could not commit session or rollback" exception is thrown when session with ...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: BRE (Expert, Fusion)
Version: BRMS 5.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 843917
TreeView+ depends on / blocked
 
Reported: 2012-08-10 08:14 UTC by Radovan Synek
Modified: 2025-02-10 03:20 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:20:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
error stacktrace (8.62 KB, text/plain)
2012-08-10 08:14 UTC, Radovan Synek
no flags Details

Description Radovan Synek 2012-08-10 08:14:24 UTC
Created attachment 603445 [details]
error stacktrace

Having several stateful knowledge sessions configured with JPA and Spring Transaction Manager. When these sessions are being disposed, the exception (see an attachment with the stacktrace) it thrown. This issue is probably connected with https://bugzilla.redhat.com/show_bug.cgi?id=839630, as these exceptions take turns.

Steps to reproduce:
this reproducer (originally for bz846981) should be usable https://github.com/droolsjbpm/droolsjbpm-integration/pull/33

see the method dispose(), the order of the sessions being disposed is important, if no exception is thrown in this method, try to reverse the order of sessions.

Comment 1 Radovan Synek 2012-08-10 08:16:59 UTC
Setting the status to "MODIFIED" as Kris has provided a fix:

https://github.com/droolsjbpm/drools/commit/96b4bae1a494b1dc8d2cb92ee263d7da209cc02f

Comment 2 Radovan Synek 2012-08-10 12:32:15 UTC
verified on 5.3.0.BRMS-P01

Comment 10 Red Hat Bugzilla 2025-02-10 03:20:29 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.


Note You need to log in before you can comment on or make changes to this bug.