Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 811998 - document what happens when child JVM service is secured
Summary: document what happens when child JVM service is secured
Alias: None
Product: RHQ Project
Classification: Other
Component: Documentation
Version: 4.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: JON 3.1.0
Assignee: Deon Ballard
QA Contact: Mike Foley
Depends On:
TreeView+ depends on / blocked
Reported: 2012-04-12 13:41 UTC by John Mazzitelli
Modified: 2013-09-05 16:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2013-09-05 16:22:01 UTC

Attachments (Terms of Use)

Description John Mazzitelli 2012-04-12 13:41:20 UTC
added this in FAQ, we should put this in the real docs somewhere:


"Q: When I import a server like JBoss EAP 5 or Tomcat, I see its child JVM resource in inventory, but it is red (DOWN). Why?

A: You probably started your server with JMX remoting enabled and secured. For example, you probably set something like the following system properties in your server:


When this happens, the JMX plugin's code will examine the command line for your server's process, see that the JMX server is remoted and secured, and try to set up its secure, remote JMX connector. When it does, it will not have the appropriate credentials to use and thus can't connect to the remote JMX MBeanServer and will consider it in a DOWN state. You must go into your new child JVM resource's Connection Properties page in the GUI and enter your valid credentials (username and password) that you set in your JMX remote access files. If you don't want RHQ to go through that remote JMX endpoint, you could try to unset all the Connection Properties for that JVM resource except the Type property - set that to "Parent". This tells RHQ to use the connection to the parent resource in order to communicate with the JVM resource. If your JVM is a child of, say, a JBossAS 4 or a JBoss EAP 5 resource, this is valid - the parent of the JVM (which is the JBossAS server resource) should be able to provide the connection to the JVM resource information."

Comment 2 Mike Foley 2013-09-05 16:22:01 UTC
old documentation issues

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