Bug 772703 - jBPM Console doesn't discard processes that no longer exist
Summary: jBPM Console doesn't discard processes that no longer exist
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: jBPM Console
Version: BRMS 5.3.0.GA
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ER6
: BRMS 5.3.0.GA
Assignee: Kris Verlaenen
QA Contact: Jiri Locker
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-09 17:38 UTC by Jiri Locker
Modified: 2020-04-27 01:12 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)

Description Jiri Locker 2012-01-09 17:38:44 UTC
Description of problem:
I have created some processes and had them listed in the jBPM Console's process overview. When I delete one ore more of the processes and refresh the process overview, the processes don't disappear.


Version-Release number of selected component (if applicable):
ER2

How reproducible:
always

Steps to Reproduce:
1. create some processes in Guvnor and build the package
2. go to jBPM Console and check that the processes are listed
3. remove one process (archive in Guvnor) and rebuild the package
4. go to jBPM Console and refresh the process overview; the archived process is still there
  
Actual results:
once a process is listed in jBPM Console it won't go away after it is removed from the package served by Guvnor

Expected results:
the console should stop listing processes that no longer exist


Additional info:
restarting the server helps

Comment 2 Maciej Swiderski 2012-04-05 07:37:15 UTC
Issue is caused by missing part of removing process from a package in knowledge agent when process is not available in mointored resources. A fix and test case for it is prepared as pull request for drools-core component, can be found at: https://github.com/droolsjbpm/drools/pull/113

Comment 3 Ryan Zhang 2012-04-23 07:36:08 UTC
Update status to ON_QA. Please verify them against ER6.

Comment 4 Jiri Locker 2012-05-09 13:15:52 UTC
Fix verified in ER6.


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