cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Not a customer? Start a free trial

Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.

AppDynamics customers and established members should click the sign in button to authenticate.

Java (Java Agent, Installation, JVM, and Controller Installation)

Monitor jboss connection pool

shandi.pusghiyanto
New Poster

Monitor jboss connection pool

hy all,

 

The user has a request to monitor the jboss connection pool, then I use the link below to be able to monitor the jboss connection pool:

https://www.appdynamics.com/community/exchange/jboss-monitoring-extension/

but after I did the steps in the link, I didn't get any results,

I attach the log of machine agent and JBossDatasourceMonitor, maybe it can be a tool for you to analyze my error.

 

https://drive.google.com/open?id=1l1rMQgMCsmoz_8sM5GfJJa-aC5HUWahh

 

thanks
shandi aji

Tags (1)
By replying you agree to the Terms and Conditions of the AppDynamics Community.
Monitor jboss connection pool
5 REPLIES 5
helmy.helmy
New Poster

Hi,

I'm Following this URL: https://www.appdynamics.com/community/exchange/jboss-monitoring-extension/ to monitoring the JBoss connection pool.

In step 4 (Installation)
Restart the machine agent, check its logs and any non empty jboss_data-sources_$$.err file in the JBossDatasourceMonitor directory.

But the jboss_data-sources_$$.err is empty and the machine agent can't start when I check in Appdynamics controller web console.

The Appdynamics controller version: 4.5.15
JBoss EAP 6.4


How to start troubleshooting this issue?

Please advise.

Achmad.Sathibi
Explorer

Same like my problem, i have same experience with jboss extension.

Appdynamics support any idea ?

Please help...

 

Many thanks

Vishaka.Sekar
AppDynamics Team

Thanks for reaching out to us. While this is an author supported extension and is not officially supported by AppDynamics, we will troubleshoot any basic machine agent configuration related issues on a best-effort basis. 

 

To troubleshoot missing custom metrics, please go through every step in the Extensions Troubleshooting Document.

 

If the issues still persist, please email us at [Email redacted]  with the following for us to assist you better:

 

1. monitor.xml (<MachineAgentHome>/monitors/<ExtensionMonitor>)

2. Controller-info.xml (<MachineAgentHome>/conf/controller-info.xml)

3. Enable Machine Agent `DEBUG` logging by changing the level values of the following logger elements from `INFO` to `DEBUG` in `<MachineAgent>/conf/logging/log4j.xml`:


<logger name="com.singularity">

<logger name="com.appdynamics">

4. After letting the Machine Agent run for 10-15 minutes, attach the complete `<MachineAgentHome>/logs/` directory.

 

^ Post edited by @Ryan.Paredez to redact the email. Please do not share emails publicly on posts. 

shandi.pusghiyanto
New Poster

hy @Vishaka.Sekar 

 

here is attach logs from the machine agent.

[Log File redacted]

 

thanks
shandi aji P

 

^ Post edited by @Ryan.Paredez to remove log file. Please do not share or attach log files to community posts for security and privacy reasons. 

Vishaka.Sekar
AppDynamics Team

 For faster resolution and tracking, can you please send the attachment in an email to [Redacted]? That will ensure that the support team responds to your queries better and faster. 


Thanks, 

Vishaka 

 

^ Post edited by @Ryan.Paredez to remove email from post. We suggest not sharing emails in community posts.