Bug 1332536 - Process instance starting with timer event can not be aborted
Summary: Process instance starting with timer event can not be aborted
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Shelly McGowan
QA Contact: Jozef Marko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-03 12:30 UTC by Jozef Marko
Modified: 2020-03-27 19:41 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
fedora23, eap-6.4.7.GA
Last Closed: 2020-03-27 19:41:39 UTC
Type: Bug


Attachments (Terms of Use)

Description Jozef Marko 2016-05-03 12:30:12 UTC
Description of problem:
User has possibility to model process starting with a timer event. In this timer event can be specified a time cycle in which process will be repeatedly started. After the project is built and the process instance created, user has possibility to abort the given process instance. However, processes starting with timer event are not aborted properly.

Version-Release number of selected component (if applicable):
6.3.0.CR2

Steps to Reproduce:
1. Create new project
2. Create new business process
3. Model process as: TimerStart -> SriptTask -> EndEvent
4. Set time cycle for TimerStart to: 10s
5. Set script for ScriptTask to: System.out.println("xxx");
6. Save process
7. Build and deploy project
8. Go to process definitions
9. Start the given process
10. See output of app. server
11. Go to the process instances
12. Abort the given process instance
13. See output of app. server

Actual results:
In both steps 10. and 13. user can see new string xxx every 10 second

Expected results:
In step 10. user can see new string xxx every 10 second
In step 13. user can not see any new new string xxx


Additional info:
Process instance is aborted only if project is undeployed


Note You need to log in before you can comment on or make changes to this bug.