ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

JMX Folder goes missing ::Fuse 20.9 Agent

book

Article ID: 212351

calendar_today

Updated On:

Products

CA Application Performance Management (APM / Wily / Introscope)

Issue/Introduction

Observing on few agent deployment, where when agent is deployed,  agent tree structure does not come up fully.

In addition to this, the JMX folder goes missing. although in logs, we do see agent is trying to get JMX metric from the JConsole.

 

Environment

Release : 20.2

Component : APM Agents

Resolution

JMX Filters in jmx.yml. Changed permissions.

Additional Information

First suggested:

Comment this line in bundle.properties:

introscope.agent.remotejmx.system.s1.mbeanPatternsBlackList=*:*

 

Did not help.

 

With the blacklist line commented out,now trying to subscribe to MBeans, but seeing a lot of errors like:

 [DEBUG] [IntroscopeAgent.JMXClient] Error creating Subscriber for attribute - CollectionUsageThreshold
 

Not sure if it's failing for all subscriptions.

 

Also:

Turn on TRACE log for JMXClient module by adding following line to IntroscopeAgent.profile:

log4j.logger.IntroscopeAgent.JMXClient=TRACE#com.wily.util.feedback.Log4JSeverityLevel, logfile