Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1167738

Summary: BitronixRollbackException thrown instead of performing rollback
Product: [Retired] JBoss BPMS Platform 6 Reporter: Tomas Livora <tlivora>
Component: jBPM CoreAssignee: Alessandro Lazarotti <alazarot>
Status: CLOSED EOL QA Contact: Radovan Synek <rsynek>
Severity: medium Docs Contact:
Priority: high    
Version: 6.1.0CC: kverlaen
Target Milestone: ER3   
Target Release: 6.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1195130 (view as bug list) Environment:
Last Closed: 2020-03-27 20:11:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1195130    
Attachments:
Description Flags
BZ958390RuntimeExceptionAfterTimerTest results on CR1 none

Description Tomas Livora 2014-11-25 10:37:26 UTC
Created attachment 961136 [details]
BZ958390RuntimeExceptionAfterTimerTest results on CR1

Description of problem:
BitronixRollbackException and other exceptions are thrown instead of transaction rollback.

Version-Release number of selected component (if applicable):
jBPM 6.2.0 CR1

How reproducible:
https://gitlab.mw.lab.eng.bos.redhat.com/bxms/brms/blob/master/test-jbpm-regression/src/test/java/com/bpms/customer/BZ958390RuntimeExceptionAfterTimerTest.java
https://gitlab.mw.lab.eng.bos.redhat.com/bxms/brms/blob/master/test-jbpm-regression/src/test/resources/com/bpms/customer/RuntimeExceptionAfterTimer.bpmn2

Steps to Reproduce:
1. Create a process with intermediate timer event and throw exception after it.
2. Run the process and see the results.

Actual results:
A lot of different exceptions are thrown.

Expected results:
The transaction rollback should be performed without any problems.

Additional info:
This issue was introduced between versions Beta3 and CR1, and it might be related to bug 958390.

Comment 1 Maciej Swiderski 2014-11-25 17:48:49 UTC
fixed by ensuring that timers without fire next time date are not added to timer instances job

jbpm
master:
https://github.com/droolsjbpm/jbpm/commit/37097db037f0dbfdfdc875fdfb664e2db862f17b

6.2.x:
https://github.com/droolsjbpm/jbpm/commit/ccd47359f9433115dff329a19826326ee2ea8d68

Comment 2 Tomas Livora 2014-12-16 11:59:29 UTC
Verified on BPMS 6.1.0 ER3