Deploying Agent in an Alpine container crashes the application

book

Article ID: 140400

calendar_today

Updated On:

Products

CA Application Performance Management Agent (APM / Wily / Introscope) CA Application Performance Management (APM / Wily / Introscope) INTROSCOPE

Issue/Introduction

Running the tomcat based application Camunda inside an Alpine linux container with the APM java the agent enabled causes a crash with Sig 11.

 

A fatal error has been detected by the Java Runtime Environment:
SIGSEGV (0xb) at pc=0x00007f376209c42c, pid=141, tid=0x00007f37488e8b10

JRE version: OpenJDK Runtime Environment (8.0212-b04) (build 1.8.0212-b04)
Java VM: OpenJDK 64-Bit Server VM (25.212-b04 mixed mode linux-amd64 compressed oops)
Derivative: IcedTea 3.12.0
Distribution: Custom build (Sat May 4 17:33:35 UTC 2019)
Problematic frame:
C [ld-musl-x8664.so.1+0x4942c] _getdelim+0x1b7

 

Cause

The problem is caused by the attempt to load the agent platform monitor libraries in an unsupported operating system environment. 

Environment

Release : 10.7.0

Component : APM Agents

Operating system: Alpine Linux

Application Camunda

Resolution

When running inside a container environment the default configuration to use is the Microservices profile


https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/application-performance-management/10-7/implementing-agents/java-agent/install-the-java-agent/configure-application-server-to-use-the-java-agent/microservices.html


This has the following value set for the platform monitor


introscope.agent.platform.monitor.system=UnsupportedOS



Setting this value disables the platform monitor and prevents the crash.


At present this profile is not an available option in APM Command Center for APM 10.7 On Premise installations. It is however available in the current SaaS release.