CA Java Agent to JBOSS EAP 7.1

[Emerson Vargas]

Hi everyone,

I have the following environment:
- APM Enterprise Manager MOM version 10R7 - Release 10.7.0.235 (build 994301)
- Server with JBOSS EAP 7.1 in Standalone configuration
- Java Agent Version 10.5.1 Release 10.5.1.8


I have installed CA Java Agent using the JBOSS Standalone configuration steps as mentioned in the installation guide as available on Broadcom Support portal.

I already have made changes to the agent profile (IntroscopeAgent.profile) to connect with our EM on port 5001. Our EM is configured correctly to this port too. We can connect using telnet.
- agentManager.url.1=X.X.X.X:5001

I have made the desired changes to JBOSS standalone.conf file as required by the CA Java agent, but it isn't showing up in the CA Workstation.

I don't have any log generated by the CA Java Agent.

We believe that something in the environment is impacting/conflicting with CA Java Agent, but we haven't been able to figure out what exactly.

Is there any way to know what is going on with my Java Agent?

PS: I have others JBOSS server with the same version of the Java Agent (JBOSS using the same configuration) whose is showing in the CA Workstation.

Best Regards,
Emerson Vargas

[Gordon Preston]

Hi Emerson,

You can turn on verbose class loading in the JVM (verbose:class) to see if the any of the agent files are getting loaded at all.

Also, you can check the output of the 'lsof -p <pid of jvm>' to see if the Agent.jar file is included in the output.

Do you have any other monitoring solutions in place on the JBoss server as they can sometimes conflict with the APM agent as seen in this KD article with WebLogic and the Dynatrace agent?
https://knowledge.broadcom.com/external/article?articleId=136868

Hope this helps.

Regards,
Gordon

[Emerson Vargas]

Hi Gordon,

My root cause was exactly the Dynatrace agent installed in my environment.

The resolution was uninstall the Dynatrace agent.

Now my Agents is showing up in the CA Workstation.

Thanks for your help.

Regards,

------------------------------
Associate Service Consultant
HCL Technology
------------------------------

[Haruhiko Davis]

10.5.x agents do not support the use of 'agentManager.url.x' in the agent profile or as a Java system property. You will need to upgrade to 10.7+.

------------------------------
Custom Solution Architect
Broadcom
------------------------------

[Haruhiko Davis]

https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/application-performance-management/10-5/implementing-agents/java-agent/install-the-java-agent/configure-application-server-to-use-the-java-agent/jboss.html

------------------------------
Custom Solution Architect
Broadcom
------------------------------

[Haruhiko Davis]

One last note:

APM 10.5 End Of Service (EOS) is scheduled by year's end. Now would be a good time to upgrade your agents to 10.7+.

https://support.broadcom.com/external/content/release-announcements/CA-APM-Release-and-Support-Lifecycle-Dates/3058

------------------------------
Custom Solution Architect
Broadcom
------------------------------

[Emerson Vargas]

Hi Davis,

I will schedule an upgrade of my agents to 10.7+ version.

Thanks for sharing the information about  the End Of Service (EOS).

Regards,



------------------------------
Associate Service Consultant
HCL Technology
------------------------------