Here's an example of the superfluous warnings: 2012-02-13 11:27:10,269 WARN [ResourceDiscoveryComponent.invoker.daemon-1] (org.rhq.plugins.jbossas5.ApplicationServerDiscoveryComponent)- Client JAR [file:/home/ips/Applications/jboss-eap-5.1.2/jboss-as/lib/jboss-classpool.jar] does not exist or is not readable (note, this JAR may not be required for some app server versions). 2012-02-13 11:27:10,270 WARN [ResourceDiscoveryComponent.invoker.daemon-1] (org.rhq.plugins.jbossas5.ApplicationServerDiscoveryComponent)- Client JAR [file:/home/ips/Applications/jboss-eap-5.1.2/jboss-as/lib/jboss-classpool-scoped.jar] does not exist or is not readable (note, this JAR may not be required for some app server versions). 2012-02-13 11:27:10,272 WARN [ResourceDiscoveryComponent.invoker.daemon-1] (org.rhq.plugins.jbossas5.ApplicationServerDiscoveryComponent)- Client JAR [file:/home/ips/Applications/jboss-eap-5.1.2/jboss-as/common/lib/jboss-as-profileservice.jar] does not exist or is not readable (note, this JAR may not be required for some app server versions). Several of them get logged every time an AS or EAP instance is discovered or re-discovered. Besides cluttering the log, they could falsely alarm users.
per triage 2/13/2012 (asantos, crouch, foley, loleary)
master commit bed4b9a72f3f6ec19939e82a9fd27e392dc85a9c Author: Jay Shaughnessy <jshaughn> Date: Wed Aug 20 10:48:59 2014 -0400 I changed the offensive WARN-level message to DEBUG level. It's not really possible to distinguish between non-existent and non-readable, or to know which versions require which JAR. If there is a failure then we can turn on debug to see the message. release/jon3.3.x commit 038e60bf5b05101680a5693a18d2f492c287230e Author: Jay Shaughnessy <jshaughn> Date: Wed Aug 20 10:57:23 2014 -0400 Cherry-Pick master bed4b9a72f3f6ec19939e82a9fd27e392dc85a9c
Moving to ON_QA as available for test with the following brew build: https://brewweb.devel.redhat.com//buildinfo?buildID=381194
Created attachment 936171 [details] eap5_debug_log
verified in JON 3.3 ER02 'JAR may not be required for some app server versions' is logged as Debug message. screen-shot attached