MBeans problems with DX-APM - Java agent version 2023.6
search cancel

MBeans problems with DX-APM - Java agent version 2023.6

book

Article ID: 367077

calendar_today

Updated On:

Products

DX APM SaaS

Issue/Introduction

Mainframe team is using Java agent version 21.4 without any issue, but when they tried to upgrade it with latest version i.e. 2023.6 below issues appeared.

Initially following error appeared
E CWWKE0701E: bundle com.ibm.cics.wlp.bundlepart.impl:1.100.0 in the messages.log

When team started testing some code to disable and enable JVMEndpoints using the MBeans an additional error appeared in the messages:

JVMK4N01 E [EVENT_RESPONDER] [com.ibm.cics.delegate.impl.jvmevents] [EndpointSPIController] @Error: setEndpoint() - Unexpected exception. See stack trace for details, java.lang.reflect.UndeclaredThrowableException

The case was raised for IBM as well and they mentioned its issue with latest agent. 

Resolution

The instrumentation of this spring boot agent extension was designed to set the frontend application name as needed to have a more recognizable name for metric reporting.  While some spring boot application may be more lenient about such a mechanism, others may choke up on this intrusive behavior and treat it as an offensive conflict.

Workaround is to modify the agent configuration and skip the conflicting APMIA spring-boot agent extension.Workaround is to modify the agent configuration and skip the conflicting APMIA spring-boot agent extension.