AppD Archive

Jboss EAP 6.1 thread pool detection

CommunityUser
Splunk Employee
Splunk Employee

I am running JBoss EAP 6.1 with below settings in standalone.xml

Below creates a thread pool named "http-executor"

<subsystem xmlns="urn:jboss:domain:threads:1.1">
            <blocking-bounded-queue-thread-pool name="http-executor">
                <core-threads count="200"/>
                <queue-length count="100"/>
                <max-threads count="2048"/>
                <keepalive-time time="60" unit="seconds"/>
            </blocking-bounded-queue-thread-pool>
        </subsystem>

 Then this thread pool is used in jboss web settings as below indicated in BOLD:

<subsystem xmlns="urn:jboss:domain:web:1.4" default-virtual-server="default-host" native="false">
            <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" executor="http-executor"/>
            <connector name="https" protocol="HTTP/1.1" scheme="https" socket-binding="https" secure="true">
                <ssl name="https" password="GSPxbec12" certificate-key-file="C:\jboss\bin\ssl.keystore" protocol="TLS"/>
            </connector>
            <virtual-server name="default-host" enable-welcome-root="true">
                <alias name="localhost"/>
                <alias name="example.com"/>
            </virtual-server>
        </subsystem>

 Now I want to track the no of threads and other related information in appdynamics like I am able to do for http:0.0.0.0:80 under metric browser ->node->JMX->web container runtime->.

Basically I want to get the specific information related to the thead pool created by me.

 

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Interested if this ever got resolved. We are having similar challenges with EAP 6.2 / Jboss 7.3.

Under EAP 4.3 / Jboss 4.2.1 we used to get a whole swag of JMX Metrics including

jboss.web:type=ThreadPool,* 

jboss.jca:service=ManagedConnectionPool,*

jboss.web:type=Manager,*

However with the changes to EAP/Jboss container strategies in JBoss 5/6/7 all of these metrics are now reported as zero in AppDynamics.

Does AppDynamics have any plans to support EAP 6.2 based Metrics (c.f Jboss 4.N variant only) 

Ideally hoping to just get the standard ones back - I have been able to get some of this back using the CLI interface. So tempted to try and create a plugin - for the machine agent!!!

0 Karma

Arun_Dasetty
Super Champion

Hi Rippon and Andrew,

I wonder the default JMX config for jboss server under Configure -> Instrumentation -> JMX screen in controller UI might not match mbean pattern for different versions, Can you check if the target metrics are exposed in jconsole and if yes then please check whether they are also shows up on mbean browser for the same node dashbaord -> jmx -> mbean browser section as refrerred in doc link :

https://docs.appdynamics.com/display/PRO39/Configure+JMX+Metrics+from+MBeans#ConfigureJMXMetricsfrom...

https://docs.appdynamics.com/display/PRO39/Monitor+JMX+MBeans

Let us know if that information helps.

Regards,

Arun

0 Karma
Get Updates on the Splunk Community!

See just what you’ve been missing | Observability tracks at Splunk University

Looking to sharpen your observability skills so you can better understand how to collect and analyze data from ...

Weezer at .conf25? Say it ain’t so!

Hello Splunkers, The countdown to .conf25 is on-and we've just turned up the volume! We're thrilled to ...

How SC4S Makes Suricata Logs Ingestion Simple

Network security monitoring has become increasingly critical for organizations of all sizes. Splunk has ...