policy server coredump is getting created with APMSSO 13.2

Products

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

Issue/Introduction

When APMSSO 13.2 is configured with Siteminder Policy server 12.8 sp1, seeing core files generated by stop command on policy servers (stop-all or stop-ps).

When the APM configuration from XPSConfig is removed, no longer see the coredump.

 

Cause

The call stack of the crashing thread is

#0 0x00007f4de75a2207 in raise () from /weish04/nfcu/core-lib-data/libs/lib64/libc.so.6
#1 0x00007f4de75a38f8 in abort () from /weish04/nfcu/core-lib-data/libs/lib64/libc.so.6
#2 0x00007f4d4792d4b5 in os::abort(bool) () from /weish04/nfcu/core-lib-data/libs/opt/CA/jdk1.8.0_172/jre/lib/amd64/server/libjvm.so
#3 0x00007f4d47ad1623 in VMError::report_and_die() () from /weish04/nfcu/core-lib-data/libs/opt/CA/jdk1.8.0_172/jre/lib/amd64/server/libjvm.so
#4 0x00007f4d479337af in JVM_handle_linux_signal () from /weish04/nfcu/core-lib-data/libs/opt/CA/jdk1.8.0_172/jre/lib/amd64/server/libjvm.so
#5 0x00007f4d479297d3 in signalHandler(int, siginfo*, void*) () from /weish04/nfcu/core-lib-data/libs/opt/CA/jdk1.8.0_172/jre/lib/amd64/server/libjvm.so
#6 <signal handler called>
#7 0x00007f4d76030416 in ?? ()
#8 0x00007f4d6fffce30 in ?? ()
#9 0x0000000000000000 in ?? ()

This still is related to  APM Metric thread. It appears APM lib is already unloaded. Maybe it woke up at the wrong time and the function instructions no longer in memory since it' is no longer loaded.

Once customer removed APM module from XPSConfig, we no longer get core dump when stopping policy server.
 

Environment

Siteminder Policy Server PS - 12.8 sp1
APMSSO 13.2
RHEL

Resolution

The issue is identified and Engineering has provided a fix. 

Please open a support case and request for the fix 

Ref: Defect : DE406345