Bug 824509 - (solaris only) agent only detects jmx-enabled processes own by agent user
Summary: (solaris only) agent only detects jmx-enabled processes own by agent user
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Agent
Version: JON 3.1.0
Hardware: x86_64
OS: Solaris
high
high
Target Milestone: ---
: JON 3.2.0
Assignee: Thomas Segismont
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-23 15:54 UTC by Viet Nguyen
Modified: 2013-09-13 10:05 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-09-13 10:05:59 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 799532 0 high CLOSED JMX plugin discovery causes Java processes to output stack traces 2021-02-22 00:41:40 UTC

Internal Links: 799532

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


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