Description of problem: When the JON server starts up, it logs a number of JBAS015960 warnings complaining about invalid classpath entries for a number of various libraries. Not sure if these are really valid, because otherwise the server seems to function normally, but seeing 39 of such warnings (some of them duplicated) in the logs is somewhat disconcerting. Version-Release number of selected component (if applicable): JON 3.2.0.ER4 How reproducible: alwyas Steps to Reproduce: 1. start up ER4
The fix is not as simple as suggested in the (hidden) comment above. Because it's out of our control, these are 3rd party libs and EAP generated messages. Master commit ab38128e3d4d5b1e38005bc108783b36f9ce2c9f Author: Jay Shaughnessy <jshaughn> Date: Fri Sep 5 09:27:54 2014 -0400 Add logger subsystem filtering to omit the error codes we don't want to Filtering out the "invalid class-path" as well as a few other annoying warnings. - added installer support to set the filter in the standalone-full.xml. release/jon3.3.x commit b71dc7007c3a5aff4b13022c2e7d16c8a8d521e5 Author: Jay Shaughnessy <jshaughn> Date: Fri Sep 5 09:27:54 2014 -0400 (cherry picked from commit ab38128e3d4d5b1e38005bc108783b36f9ce2c9f) Signed-off-by: Jay Shaughnessy <jshaughn>
*** Bug 1078497 has been marked as a duplicate of this bug. ***
Moving to ON_QA as available for test with the following brew build: https://brewweb.devel.redhat.com//buildinfo?buildID=385149
verified on Version : 3.3.0.ER03 Build Number : 4aefe39:44e33a4
*** Bug 1078494 has been marked as a duplicate of this bug. ***