Bug 847231 - "Could not commit session or rollback" exception is thrown when session with Spring Transaction Manager is being disposed
"Could not commit session or rollback" exception is thrown when session with ...
Status: VERIFIED
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: BRE (Expert, Fusion) (Show other bugs)
BRMS 5.3.1
Unspecified Unspecified
unspecified Severity high
: ---
: ---
Assigned To: Tihomir Surdilovic
Radovan Synek
:
Depends On:
Blocks: 843917
  Show dependency treegraph
 
Reported: 2012-08-10 04:14 EDT by Radovan Synek
Modified: 2013-10-10 20:19 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


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

  None (edit)
Description Radovan Synek 2012-08-10 04:14:24 EDT
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 04:16:59 EDT
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 08:32:15 EDT
verified on 5.3.0.BRMS-P01

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