Bug 1127875 – Process service resources continues to monitor old process even after process no longer exists or after piql/pid file has changed

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1127875 - Process service resources continues to monitor old process even after process no longer exists or after piql/pid file has changed

Summary:	Process service resources continues to monitor old process even after process...

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	JBoss Operations Network
Classification:	JBoss
Component:	Plugin -- Other (Show other bugs)
Sub Component:
Version:	JON 3.1.2
Hardware:	Unspecified Unspecified

Priority	unspecified Severity medium
Target Milestone:	ER01
Target Release:	JON 3.3.0
Assigned To:	RHQ Project Maintainer
QA Contact:	Filip Brychta
Docs Contact:

URL:
Whiteboard:
Keywords:	Triaged

Depends On:	1100609 1109439
Blocks:	1091134 1127876
	Show dependency tree / graph

Reported:	2014-08-07 14:06 EDT by John Mazzitelli
Modified:	2014-12-11 09:02 EST (History)
CC List:	6 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	A bug in the JON "Platform Plug-in" resulted in connection setting changes to the "Process" resource to be ignored. When the user changed the Connection Settings of a Process service (for example, changed the PIQL query or the PID file path), the plug-in kept monitoring the same process as it was before the change, until this process terminated or the agent was restarted. The ProcessComponent class is now fixed to take Connection Settings into account immediately after changes. The plug-in now immediately monitors the process denoted by the Connection Settings after they were changed.
Story Points:	---
Clone Of:	1109439
Environment:
Last Closed:	2014-12-11 09:02:46 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Knowledge Base (Solution)	795963	None	None	None	Never

Groups: None (edit)

Comment 1 John Mazzitelli 2014-08-07 16:00:44 EDT

this looks to already be in the release/jon3.3.x branch:

# On branch release/jon3.3.x
nothing to commit (working directory clean)
The previous cherry-pick is now empty, possibly due to conflict resolution.

Comment 2 Simeon Pinder 2014-08-19 19:50:47 EDT

Moving to ON_QA as available to test in the following brew build:

https://brewweb.devel.redhat.com//buildinfo?buildID=379025

Comment 3 Filip Brychta 2014-08-27 10:10:07 EDT

Verified on 
Version :	
3.3.0.ER01.1
Build Number :	
9941660:f3aa7e7

Comment 6 John Mazzitelli 2014-10-13 09:40:08 EDT

I do not know why this has NEEDINFO from me - I don't think i've been asked anything. Clearing the NEEDINFO field. If there is something needed from me, let me know what it is.

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