Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 824509

Summary:	(solaris only) agent only detects jmx-enabled processes own by agent user
Product:	[JBoss] JBoss Operations Network	Reporter:	Viet Nguyen <vnguyen>
Component:	Agent	Assignee:	Thomas Segismont <tsegismo>
Status:	CLOSED NOTABUG	QA Contact:	Mike Foley <mfoley>
Severity:	high	Docs Contact:
Priority:	high
Version:	JON 3.1.0	CC:	myarboro, tsegismo
Target Milestone:	---
Target Release:	JON 3.2.0
Hardware:	x86_64
OS:	Solaris
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-13 10:05:59 UTC	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 Viet Nguyen 2012-05-23 15:54:17 UTC

Description of problem:
In Solaris 11 agent only detects local jmx processes own by agent user not by other users.


Version-Release number of selected component (if applicable):
JON 3.1 ER4
Solaris 11 i386
JDK 1.6.0.26 b03

How reproducible:
100%

Steps to Reproduce:
1. As agent user run a java program with jxm enabled eg
-Dcom.sun.management.jmxremote.port=45123 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false

2. run agent discovery. verify the java process is being detected

3. As another user run the same java program with different jmxremote port

4. run agent discovery
  
Actual results:
agent does not detect jmx processes owned by non-agent user

Expected results:
In RHEL6 and windows2007 agent detects all local jmx processes regardless of process owner. 

Additional info:

Comment 1 Mike Foley 2012-05-29 14:41:08 UTC

per BZ Triage 5/29/2012 (ccrouch, loleary, asantos, mfoley, myarborough) moving these to JON 3.1.1 or later

Comment 3 Thomas Segismont 2013-09-13 10:05:59 UTC

This is not a bug, you must give the user running the agent sufficient permissions or run it as root (edit /etc/user_attr file and give proc_owner privilege to the user running the agent)

See https://jira.hyperic.com/browse/SIGAR-101