Bug 780692 (SOA-3141) - the Exception on rollback hides the original Exception on commit in DbPersistenceService.endTransaction()
Summary: the Exception on rollback hides the original Exception on commit in DbPersist...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-3141
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBPM - within SOA, JBPM - standalone
Version: 5.1.0 GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.2.0 GA,5.2.0.ER2
Assignee: Julian Coleman
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-30 10:09 UTC by Toshiya Kobayashi
Modified: 2011-11-03 10:04 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-03 10:04:59 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-3141 0 None None None Never

Description Toshiya Kobayashi 2011-06-30 10:09:03 UTC 
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000007CaHE&sfdc.override=1
project_key: SOA

Platform JIRA for [JBPM-3274] the Exception on rollback hides the original Exception on commit in DbPersistenceService.endTransaction()
Comment 1 Toshiya Kobayashi 2011-06-30 10:09:37 UTC 
Link: Added: This issue incorporates JBPM-3274
Comment 2 Anne-Louise Tangring 2011-08-08 16:08:29 UTC 
This should be fixed in the jBPM version we pick up. Resovle as part of build, please. Thanks.
Comment 3 Douglas Palmer 2011-09-09 22:16:26 UTC 
This was fixed in jBPM 3.2.11.
Comment 4 David Le Sage 2011-09-27 02:43:34 UTC 
Release Notes Docs Status: Added: Documented as Resolved Issue
Writer: Added: dlesage
Release Notes Text: Added: https://issues.jboss.org/browse/SOA-3141

An exception that occurred on rollback was obscuring the original exception on commit in DbPersistenceService.endTransaction(). As a result, users could not see the cause of the problem.  An upgrade to the jBPM has fixed this issue so users can now see the errors.
Comment 5 Jiri Pechanec 2011-11-03 10:04:59 UTC 
Verified in ER6
Note You need to log in before you can comment on or make changes to this bug.