Bug 780084 (SOA-2452) - [JBPM-2964] Throw the exception on commit when both commit and rollback fail
Summary: [JBPM-2964] Throw the exception on commit when both commit and rollback fail
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2452
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBPM - within SOA, JBPM - standalone
Version: 4.3 CP04 GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Alejandro Guizar
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-21 07:32 UTC by Toshiya Kobayashi
Modified: 2011-07-18 23:57 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 780085 (view as bug list)
Environment:
Last Closed: 2011-07-18 23:57:45 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-2452 0 None None None Never

Description Toshiya Kobayashi 2010-10-21 07:32:19 UTC 
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000003hTEv&sfdc.override=1
project_key: SOA

Platform JIRA for [JBPM-2964] Throw the exception on commit when both commit and rollback fail
Comment 1 Toshiya Kobayashi 2010-10-21 07:38:45 UTC 
Link: Added: This issue incorporates JBPM-2964
Comment 2 Alejandro Guizar 2010-10-28 03:01:51 UTC 
Project issue JBPM-2964 resolved.
Comment 3 Len DiMaggio 2011-02-14 15:42:48 UTC 
Verified in the ER9 source.
Comment 4 David Le Sage 2011-02-25 04:34:30 UTC 
Temporarily reopening to update release note info.
Comment 5 David Le Sage 2011-02-25 04:38:19 UTC 
Release Notes Docs Status: Added: Documented as Resolved Issue
Writer: Added: dlesage
Release Notes Text: Added: https://issues.jboss.org/browse/JBPM-2964

Exception handling has been improved.  The rollback() method now catches and returns any exception thrown while rolling back the transaction and logs it. Previously, if the commit() method threw an exception in DbPersistenceService.endTransaction(), rollback() was called and then, if rollback() also threw an exception, a client application would receive it, which was not optimal behaviour.
Comment 6 Toshiya Kobayashi 2011-06-30 08:21:14 UTC 
JBPM-2964 doesn't resolve the original problem. Re-opened.
Comment 7 Toshiya Kobayashi 2011-06-30 09:26:36 UTC 
Re-close as this is a released issue.
Note You need to log in before you can comment on or make changes to this bug.