Document URL: https://access.redhat.com/site/documentation/en-US/JBoss_Operations_Network/3.1/html-single/Installation_Guide/index.html Section Number and Name: Describe the issue: RHQ_AGENT_JAVA_EXE_FILE_PATH and RHQ_AGENT_JAVA_HOME are only mentioned in the 8.4.2. Running the Agent as a Daemon or init.d Service [1] although if above variables are not defined, JBoss ON Agent will not start and customer's will get message: "There is no JVM available. Please set RHQ_AGENT_JAVA_HOME or RHQ_AGENT_JAVA_EXE_FILE_PATH appropriately." [1] https://access.redhat.com/site/documentation/en-US/JBoss_Operations_Network/3.1/html-single/Installation_Guide/index.html#starting-agent-rhel Suggestions for improvement: Additional information:
Although the documentation should provide supplemental information, this seems to be on the border of a bug in my opinion. The fact that that JBoss ON requires environment configuration different then the typical Java application seems to indicate that the implementation is at fault. Bottom line, the agent should probably do a better job at resolving the location of "java". For the documentation, RHQ_AGENT_JAVA_EXE_FILE_PATH and RHQ_AGENT_JAVA_HOME should only be referenced as an alternative option in the event that JAVA_HOME can not be used. Therefore, instead of emphasizing the special environment properties of RHQ_AGENT... JAVA_HOME should be emphasized as a requirement. For example: In order to start the JBoss ON agent, the environment variable JAVA_HOME must be defined and point to a valid Java installation. Alternatively, if JAVA_HOME can not be used, RHQ_AGENT_JAVA_HOME or RHQ_AGENT_JAVA_EXE_FILE_PATH can be used. Please note that if RHQ_AGENT_JAVA_EXE_FILE_PATH is used, its value must be the absolute path to the Java binary (i.e. /opt/java/jre1.6.0/bin/java).
Mass closure of bugs modified in 2013. All of these are in the currently-published docs.