We need to get this fix into the product branch. +++ This bug was initially created as a clone of Bug #1100609 +++ Description of problem: When you change the plugin configuration of a Process resource (piql, pid file, full process tree), the resource component keeps monitoring the old process, as long as it stays up. Version-Release number of selected component (if applicable): 4.11 How reproducible: Always Steps to Reproduce: 1.Import a Process Service to match process A 2.Check availability and metrics 3.Change plugin configuration to match process B 4.Shutdown process B Actual results: If process A is still up, the Process Service reports UP avail and metrics are still collected Expected results: The Process Service should report DOWN avail and metrics shouldn't be collected Additional info: This problem was found while working on analysis of Bug 1091134 --- Additional comment from Thomas Segismont on 2014-05-23 04:28:59 EDT --- Fixed in master commit 481dbc2a158f44a73d37465c2676fddb1b13e9a4 Author: Thomas Segismont <tsegismo> Date: Fri May 23 10:24:45 2014 +0200 Wrapped config params in a class Null out config instance and process instance when stopping component Do not fill the metric report if the process is DOWN
commit to release/jon3.2.x : d7c528b0cd349237e753f4df81968ae1149be231
Moving to ON_QA as this is available for test in JON 3.2.3 ER01 build: http://jon01.mw.lab.eng.bos.redhat.com:8042/dist/release/jon/3.2.3.GA/8-14-14/
It's working as expected Version: JBoss Operations Network Version : 3.2.0.GA Update 03 Build Number : bca1bc8:e19c43d GWT Version : 2.5.0 SmartGWT Version : 3.0p