Not able to get JMX metrics for JBOSS 6.4 and getting a Parsing error in the logs.
search cancel

Not able to get JMX metrics for JBOSS 6.4 and getting a Parsing error in the logs.

book

Article ID: 39875

calendar_today

Updated On:

Products

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

Issue/Introduction

 Problem:

 

 Installed Java Agent 10.1 with JBOSS 6.4 and JMX metrics were not seen in the Investigator.  In the logs, the following error is found.

 

2016-03-09 12:20:35,579 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.unit."introscope-jboss-service.xml".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."introscope-jboss-service.xml".PARSE: JBAS018733: Failed to process phase PARSE of deployment "introscope-jboss-service.xml"

        at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [jboss-as-server-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45]

        at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]

Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS017224: Failed to parse service xml ["/content/introscope-jboss-service.xml"]

        at org.jboss.as.service.ServiceDeploymentParsingProcessor.deploy(ServiceDeploymentParsingProcessor.java:102)

        at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [jboss-as-server-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]

        ... 5 more

Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[5,1]

Message: Unexpected element 'service'

        at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108)

        at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)

        at org.jboss.as.service.ServiceDeploymentParsingProcessor.deploy(ServiceDeploymentParsingProcessor.java:95)

        ... 6 more

 

 Environment:

 

 APM Java Agent 10.1 and JBOSS 6.4

 

 

 Cause:

 

 Customer followed the instructions in the Agent Implementation Guide for JMX Metrics for JBOSS 6.x

 

 It was learned that JBOSS 6.4 was actually released after JBOSS 7.0 and the 6.4 was using a different folder structure than JBOSS 6.3.

 

 Resolution:

 

 By following the instructions for JBOSS 7.0 instead of the JBOSS 6.x in the guide, the JMX metrics will appear. See https://docops.ca.com/ca-apm/10-2/en/troubleshooting/agent-troubleshooting/expected-jmx-metrics-not-reported

Environment

Release: CEMUGD00200-10.1-Introscope to CA Application-Performance Management-Upgrade Mai
Component: