Bug 1125204

Summary: KieContainer stucks in memory after redeployment
Product: [JBoss] JBoss Fuse Service Works 6 Reporter: Tomas Rohovsky <trohovsk>
Component: Rules / jBPM integrationAssignee: David Ward <dward>
Status: MODIFIED --- QA Contact: Matej Melko <mmelko>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.0.0 GACC: ganandan, kejohnso, oskutka, rcernich, soa-p-jira
Target Milestone: DR4   
Target Release: 6.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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:

Description Tomas Rohovsky 2014-07-31 10:08:50 UTC
Having following scenario:

Deploy a SY application containing a KieContainer based component. Invoke the service on the component. Undeploy the application. Modify the KieModule it uses and install it to Maven repo. Deploy the application again. Invoke the service on the component. The KieContainer hasn't scanned for the updated KieModule and has loaded the KieModule that was loaded during previous deployment.

How to reproduce:
Use a reproducer from SWITCHYARD-2240.

mvn verify - you will see "expected:<[Modified ]Ciao second!> but was:<[]Ciao second!>"
mvn verify - you will see "expected:<[]Hello first!> but was:<[Modified ]Hello first!>" instead of the previous message

If you restart a server between runs, then it works as expected (doesn't work as expected ).

It might be related to SWITCHYARD-2037.

Comment 1 JBoss JIRA Server 2014-12-03 23:11:44 UTC
Rob Cernich <rcernich> updated the status of jira SWITCHYARD-2241 to Resolved