JBoss Overlays Patching breaks application if wily agent is in use
search cancel

JBoss Overlays Patching breaks application if wily agent is in use


Article ID: 203106


Updated On:


CA Application Performance Management Agent (APM / Wily / Introscope) CA Application Performance Management (APM / Wily / Introscope) INTROSCOPE DX Application Performance Management


Using JBoss 7.0 EAP platform and a patch was applied using Overlays Patching (see: https://issues.redhat.com/browse/JBEAP-7615) which makes the existing JBoss jars look like they are corrupted and install new jars in a new "overlays" directory. JBoss platform then uses those jars in .overlays but wily agent still uses the original jars and fails.

After patching JBoss the applications instrumented with the APM java agent stopped working 

The only message is wily logs is:

WARNING: Failed to load the specified log manager class org.jboss.logmanager.LogManager




Release : 10.7.0

Component : APM Agents


This is not a generic issue as other situations where JBoss EAP was patched using the mechanism did not fail. Different patches will update different files - for example the standalone.conf which will neccessitate reapplying any changes to the in relation to agent configuration

In this specific situation the solution was as follows addressed by correcting the JAVA_OPTS setting in that file