Hide Forgot
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
Fixed in master commit 481dbc2a158f44a73d37465c2676fddb1b13e9a4 Author: Thomas Segismont <tsegismo@redhat.com> 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
It's working as expected, however if we import a process resource when it is DOWN, name of the resource permanently fixed as '?' even the process up and running. Hence I opened another bug to track this issue BZ:https://bugzilla.redhat.com/show_bug.cgi?id=1132932 Version: JBoss Operations Network Version : 3.2.0.GA Update 03 Build Number : bca1bc8:e19c43d GWT Version : 2.5.0 SmartGWT Version : 3.0p
We have to verify in RHQ master branch
Bulk close of items fixed in RHQ 4.12 If you think this is not solved, then please open a *new* BZ and link to this one.