-
Bug
-
Resolution: Done
-
Critical
-
6.0.0
Description of problem:
I have a simple process: Start -> Timer -> Script Task -> End. When the Timer duration is set to 0s, the behaviour gets... strange.
Sometimes, I get an exception stacktrace (see attachment). In this case, the instance finishes. Processinstanceinfo table does not contain this instance, processinstancelog has a record of this instance as completed. Nodeinstancelog table contains only records of the instance after leaving the timer node. Start node information and information about entering the timer node are missing.
Sometimes, I get no stack trace, but the instance never finishes. Processinstanceinfo table has a record of this instance, processinstancelog has a record of this instance as active. Nodeinstancelog table contains only records of the instance up to and including entering the timer node. This instance never finishes.
Sometimes, I get no stack trace, the instance finishes. Processinstanceinfo table might or might not contain this instance, processinstancelog has two records of this instance - one as active, one as completed. Nodeinstancelog table contains records for the whole instance, all the nodes, entering and leaving.
I'd like to add that 0s is not an invalid input, just perhaps one not used often.
Version-Release number of selected component (if applicable):
BPMS 6.0 ER2
- blocks
-
RHBPMS-1348 Timer process with 0s delay does not finish on WAS
- Verified