Bug 1027339 - rhqctl status doesn't report correct PIDs for server and the underlying JVM
Summary: rhqctl status doesn't report correct PIDs for server and the underlying JVM
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Launch Scripts
Version: JON 3.2
Hardware: Unspecified
OS: Unspecified
Target Milestone: DR01
: JON 3.3.0
Assignee: Michael Burman
QA Contact: Filip Brychta
Depends On:
TreeView+ depends on / blocked
Reported: 2013-11-06 15:28 UTC by Lukas Krejci
Modified: 2014-12-11 14:02 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-12-11 14:02:26 UTC
Type: Bug

Attachments (Terms of Use)

Description Lukas Krejci 2013-11-06 15:28:20 UTC
Description of problem:
rhqctl status (--server) is supposed to give me the PID of the script that started the server (on a line called "RHQ Server") and the PID of the JBossAS process that it starts (on a line called "JBossAS Java VM child process").

These two lines report the same PID.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. start JON server
2. run  "rhqctl status"

Actual results:
the PIDs of the script and the AS JVM are the same

Expected results:
the PIDs are different and therefore should be reported correctly

Additional info:
Note that this most probably is not a regression from previous releases, because the "rhq-server.sh" script (now located in bin/internal) reports the same result.

Comment 2 Michael Burman 2014-07-03 22:19:08 UTC
The rhq-server.sh was printing the SERVER_PID instead of JVM_PID. Fixed in commit 8983596

Comment 3 Michael Burman 2014-07-04 08:07:29 UTC
Commit is in the master.

Comment 4 Simeon Pinder 2014-07-31 15:51:39 UTC
Moving to ON_QA as available to test with brew build of DR01: https://brewweb.devel.redhat.com//buildinfo?buildID=373993

Comment 5 Filip Brychta 2014-08-05 13:11:31 UTC
Verified on
Version :	
Build Number :	

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