search cancel

Upgrading to JBoss 7.3.7 and get errors with ca apm java agent 10.7

book

Article ID: 216750

calendar_today

Updated On:

Products

CA Application Performance Management (APM / Wily / Introscope)

Issue/Introduction

We are trying to upgrade to jboss eap 7.3.7 and when we start our jvm that is configured with ca apm java agent 10.7 we get the following errors

ERROR [org.jboss.as.controller.management-operation] (Agent Heartbeat) xxxx: Operation ("read-attribute") failed - address: ([("interface" => "unsecure")]) - failure description: "xxxx: Management resource '[(\"interface\" => \"unsecure\")]' not found"
ERROR [org.jboss.as.controller.management-operation] (Agent Heartbeat) xxxx: Operation ("read-attribute") failed - address: ([("interface" => "unsecure")]) - failure description: "xxxx: Management resource '[(\"interface\" => \"unsecure\")]' not found"
ERROR [org.jboss.as.controller.management-operation] (Agent Heartbeat) xxxx: Operation ("read-attribute") failed - address: ([("interface" => "unsecure")]) - failure description: "xxxx: Management resource '[(\"interface\" => \"unsecure\")]' not found"
ERROR [org.jboss.as.controller.management-operation] (Agent Heartbeat) xxxx: Operation ("read-attribute") failed - address: ([("interface" => "unsecure")]) - failure description: "xxxx: Management resource '[(\"interface\" => \"unsecure\")]' not found"

 

 

Environment

Release : 10.7.0

Component : APM Agents

Resolution

Had perform an in place upgrade of JBoss and didn't change any setting for the agent.

The startup options have invalid path since JBoss upgrade use new path.

 

Here are the original options

INTROSCOPE_OPTS="-Djava.util.logging.manager=org.jboss.logmanager.LogManager \
                 -Xbootclasspath/p:/opt/jboss/73/jboss-eap-7.3/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.1.14.Final-redhat-00001.jar:/opt/jboss/72/jboss-eap-7.2/modules/system/layers/base/org/jboss/log4j/logmanager/main/log4j-jboss-logmanager-1.1.6.Final-redhat-00001.jar:/opt/jboss/72/jboss-eap-7.2/modules/system/layers/base/org/wildfly/common/main/wildfly-common-1.4.0.Final-redhat-1.jar \
                 -Djboss.modules.system.pkgs=com.wily,com.wily.*,org.jboss.byteman,org.jboss.logmanager \
                 -javaagent:/opt/Introscope/wily/Agent.jar \
                 -Dcom.wily.introscope.agentProfile=/opt/Introscope/wily/core/config/IntroscopeAgent.profile \
                 -DagentManager.url.1=apmwly1.transunion.com:5001 \
                 -Dlog4j.appender.logfile.File=/opt/Introscope/wily/logs/IntroscopeAgent_${TU_JVM_NAME}.log \
                 -Dintroscope.autop

 

Need to change to

INTROSCOPE_OPTS="-Djava.util.logging.manager=org.jboss.logmanager.LogManager \
                 -Xbootclasspath/p:/opt/jboss/73/jboss-eap-7.3/modules/system/la
yers/base/org/jboss/logmanager/main/jboss-logmanager-2.1.14.Final-redhat-00001.j
ar:/opt/jboss/73/jboss-eap-7.3/modules/system/layers/base/org/jboss/log4j/logman
ager/main/log4j-jboss-logmanager-1.2.0.Final-redhat-00001.jar:/opt/jboss/73/jbos
s-eap-7.3/modules/system/layers/base/org/wildfly/common/main/wildfly-common-1.5.
1.Final-redhat-00001.jar\
                 -Djboss.modules.system.pkgs=com.wily,com.wily.*,org.jboss.bytem
an,org.jboss.logmanager \
                 -javaagent:/opt/Introscope/wily/Agent.jar \
                 -Dcom.wily.introscope.agentProfile=/opt/Introscope/wily/core/co
nfig/IntroscopeAgent.profile \
                 -DagentManager.url.1=apmwly-stg.transunion.com:5001 \
                 -Dlog4j.appender.logfile.File=/opt/Introscope/wily/logs/Introsc
opeAgent_${TU_JVM_NAME}.log \

-Dintroscope.autop