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

Bug 1212366

Summary: Timer process with 0s delay does not finish on WAS
Product: [Retired] JBoss BPMS Platform 6 Reporter: Pavel Kralik <pkralik>
Component: jBPM CoreAssignee: Alessandro Lazarotti <alazarot>
Status: CLOSED EOL QA Contact: Radovan Synek <rsynek>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: kverlaen, mbaluch
Target Milestone: DR1   
Target Release: 6.2.0   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 20:08:16 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: 1002554    
Bug Blocks:    

Description Pavel Kralik 2015-04-16 09:32:10 UTC 
Description of problem:
I have a simple process: Start -> Timer -> Script Task -> End. When the Timer duration is set to 0s, the process instance stays in Active tab. Other delays 1s, 2s works fine.

Version-Release number of selected component (if applicable):
WAS8 with BPMS 6.1.0.CR2

How reproducible:
Always

Steps to Reproduce:
1. Create simple process: Start -> Timer -> Script Task -> End
2. Set delay to 0s and Submit
3. Go to Active tab and see that process is active for a long time.

Actual results:
The process does not end.

Expected results:
The process should end.

Additional info:
Comment 2 Maciej Swiderski 2015-04-20 13:03:29 UTC 
fixed with this commit

jbpm
master:
https://github.com/droolsjbpm/jbpm/commit/2758ed70e0cd8ff2a92596eb4ecac10151176266
Comment 3 Pavel Kralik 2015-09-17 14:32:46 UTC 
Verified BPMS 6.2.0.ER2 with 0s, 0m, 0h, 0d.