×

Join the Conversation

Without signing in, you're just watching from the sidelines. Sign in or Register to connect, share, and be part of the Splunk Community.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Ask a Question
Stephane_Babouh
New Member
Member since: ‎11-30-2022
‎02-28-2025
Community Statistics
Posts 3
Solutions 0
Karma Given 0
Karma Received 0
Member Since ‎11-30-2022
View All

Re: JMX ActiveSession metric collection desactivat...

by in Splunk AppDynamics
‎11-30-2022 05:52 AM
‎11-30-2022 05:52 AM
Here is part of agent log file with error raised : [AD Thread-Metric Reporter1] 28 Nov 2022 22:21:27,700 WARN AgentErrorProcessor - Agent error occurred, [name,transformId]=[com.singularity.JMX.JMXDomainFinder - java.lang.ClassNotFoundException,2147483647] [AD Thread-Metric Reporter1] 28 Nov 2022 22:21:27,700 WARN AgentErrorProcessor - 4 instance(s) remaining before error log is silenced [AD Thread-Metric Reporter1] 28 Nov 2022 22:21:27,700 ERROR JMXDomainFinder - Error occurred while trying to query MBean Server during version check - java.lang.ClassNotFoundException: com.ibm.ws.security.core.SecurityContext at com.sun.jmx.mbeanserver.ClassLoaderRepositorySupport.loadClass(ClassLoaderRepositorySupport.java:232) ~[?:1.8.0_232] at com.sun.jmx.mbeanserver.ClassLoaderRepositorySupport.loadClass(ClassLoaderRepositorySupport.java:144) ~[?:1.8.0_232] at com.sun.jmx.mbeanserver.SecureClassLoaderRepository.loadClass(SecureClassLoaderRepository.java:52) ~[?:1.8.0_232] at com.singularity.ee.agent.appagent.services.jmxservice.appserver.JMXDomainsFinder.tryLoadingClassFromMBeanServerClassLoaderRepository(JMXDomainsFinder.java:347) ~[appagent.jar:Server Agent #22.5.0.33845 v22.5.0 GA compatible with 4.4.1.0 rd9770530415f19f4c5154a80772b833db8dd7cee release/22.5.0] at com.singularity.ee.agent.appagent.services.jmxservice.appserver.JMXDomainsFinder.getAttributeFromWebSphereMBeanServer(JMXDomainsFinder.java:328) ~[appagent.jar:Server Agent #22.5.0.33845 v22.5.0 GA compatible with 4.4.1.0 rd9770530415f19f4c5154a80772b833db8dd7cee release/22.5.0] at com.singularity.ee.agent.appagent.services.jmxservice.appserver.JMXDomainsFinder.checkIfMBeanServerSupportsMBeanServerInfo(JMXDomainsFinder.java:254) ~[appagent.jar:Server Agent #22.5.0.33845 v22.5.0 GA compatible with 4.4.1.0 rd9770530415f19f4c5154a80772b833db8dd7cee release/22.5.0] at com.singularity.ee.agent.appagent.services.jmxservice.appserver.JMXDomainsFinder.loadAndGetDomainMapping(JMXDomainsFinder.java:111) ~[appagent.jar:Server Agent #22.5.0.33845 v22.5.0 GA compatible with 4.4.1.0 rd9770530415f19f4c5154a80772b833db8dd7cee release/22.5.0] at com.singularity.ee.agent.appagent.services.jmxservice.appserver.common.ServerMBeanManager.run(ServerMBeanManager.java:236) ~[appagent.jar:Server Agent #22.5.0.33845 v22.5.0 GA compatible with 4.4.1.0 rd9770530415f19f4c5154a80772b833db8dd7cee release/22.5.0] at com.singularity.ee.util.javaspecific.scheduler.AgentScheduledExecutorServiceImpl$SafeRunnable.run(AgentScheduledExecutorServiceImpl.java:122) ~[appagent.jar:Server Agent #22.5.0.33845 v22.5.0 GA compatible with 4.4.1.0 rd9770530415f19f4c5154a80772b833db8dd7cee release/22.5.0] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_232] at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask$Sync.innerRun(ADFutureTask.java:320) ~[appagent.jar:Server Agent #22.5.0.33845 v22.5.0 GA compatible with 4.4.1.0 rd9770530415f19f4c5154a80772b833db8dd7cee release/22.5.0] at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask.run(ADFutureTask.java:140) ~[appagent.jar:Server Agent #22.5.0.33845 v22.5.0 GA compatible with 4.4.1.0 rd9770530415f19f4c5154a80772b833db8dd7cee release/22.5.0] at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.access$301(ADScheduledThreadPoolExecutor.java:119) ~[appagent.jar:Server Agent #22.5.0.33845 v22.5.0 GA compatible with 4.4.1.0 rd9770530415f19f4c5154a80772b833db8dd7cee release/22.5.0] at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.run(ADScheduledThreadPoolExecutor.java:238) ~[appagent.jar:Server Agent #22.5.0.33845 v22.5.0 GA compatible with 4.4.1.0 rd9770530415f19f4c5154a80772b833db8dd7cee release/22.5.0] at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.runTask(ADThreadPoolExecutor.java:694) ~[appagent.jar:Server Agent #22.5.0.33845 v22.5.0 GA compatible with 4.4.1.0 rd9770530415f19f4c5154a80772b833db8dd7cee release/22.5.0] at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.run(ADThreadPoolExecutor.java:726) ~[appagent.jar:Server Agent #22.5.0.33845 v22.5.0 GA compatible with 4.4.1.0 rd9770530415f19f4c5154a80772b833db8dd7cee release/22.5.0] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_232] ... View more

Re: JMX ActiveSession metric collection desactivat...

by in Splunk AppDynamics
‎11-30-2022 05:48 AM
‎11-30-2022 05:48 AM
Here are screenshot extracted from Metrics Browser : ... View more

JMX ActiveSession metric collection deactivated af...

by in Splunk AppDynamics
‎11-30-2022 05:47 AM
‎11-30-2022 05:47 AM
Hello, we have a Tiers application with 4 nodes corresponding to Tomcat applications. We restart these applications every evening at 22:00. For 2 of 4 nodes, metrics correspond to JMX.ActiveSession is no longer collected after startup until around 10:00 the day after. It is fixed without any action but comes again the day after. 4 Nodes are managed the same with chef deployment. Here are versions of the components : Server Agent #22.5.0.33845 v22.5.0 GA compatible with 4.4.1.0 rd9770530415f19f4c5154a80772b833db8dd7cee release/22.5.0 AppDynamics Controller build 22.10.1-611 Here is a screenshot extracted from Metrics Browser : Thanks for your suggestion and analysis of the potential root-cause. ... View more
Labels
Contact Me
Online Status
Offline
Date Last Visited
‎02-28-2025 11:10 PM