Open shift pod instrumentation issue | UMA auto attach failing/skipping the particular pod

Products

• DX SaaS
• CA Application Performance Management (APM / Wily / Introscope)
• CA Application Performance Management Agent (APM / Wily / Introscope)
• APM

Issue/Introduction

UMA version - Release 2023.9.1.27 ( 990027 )

Issue - UMA agent is not able to instrument the OpenShift pod based Java app. 

Java version - 

JVM details - vendorName='Eclipse Adoptium', vmName='OpenJDK 64-Bit Server VM'

Error Exceprts from UMA logs:

•  [INFO] [I.A.Java.UnixContainerAttacher] ProcessDescriptor{ pid='1', user='<user>', elapsedTimeInSeconds='209', commandString='java -Dlogging.config=/configs/logback-spring.xml -Dlog4j2.formatMsgNoLookups=true -jar app.jar', overridden='false', additionalData='{ 'java':JVMInfo{ binaryPath='/opt/java/openjdk/bin/java', vendorName='Eclipse Adoptium', vmName='OpenJDK 64-Bit Server VM', runtimeVersion='11.0.23+9', specificationVersion='11'}, } ', attachPropertyOverrides='{ } ', agentPropertyOverrides='{ } ' }  identified as Java process in container [ <namespace> id/<id>]
• [INFO] [I.A.Java.UnixContainerAttacher] Process 1 in container [ <namespace> id/<id> ] is being skipped since the attach mechanism has been disabled/is not available for this process. Specifically the jdk.attach module was not found.

Cause

Configuration error.

Resolution

Customer was using an incorrect image that included a JVM without the jdk.attach module. Adding the jdk.attach module solves this issue.