SATBMarkQueue::filter reported in JDK crash with SPS

Products

• SITEMINDER
• CA Single Sign On Secure Proxy Server (SiteMinder)

Issue/Introduction

Running CA Access Gateway (SPS), this one crashed once, returning stack as:

Stack: [0x00007f6444526000,0x00007f6444626000],  sp=0x00007f6444624bd8,  free space=1018k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V  [libjvm.so+0x75ffc4]  G1SATBMarkQueueSet::filter(SATBMarkQueue&)+0x74
V  [libjvm.so+0xcdd564]  SATBMarkQueueSet::flush_queue(SATBMarkQueue&)+0x14
V  [libjvm.so+0x7037d6]  G1RemarkThreadsClosure::do_thread(Thread*)+0x36
V  [libjvm.so+0xe69d7d]  Threads::threads_do(ThreadClosure*)+0x4d
V  [libjvm.so+0x70769e]  G1CMRemarkTask::work(unsigned int)+0x12e
V  [libjvm.so+0xf1d7cf]  GangWorker::loop()+0x5f
V  [libjvm.so+0xf1d82f]
V  [libjvm.so+0xe6c2ca]  Thread::call_run()+0xaa
V  [libjvm.so+0xc29413]  thread_native_entry(Thread*)+0xe3

 

Environment

  CA Access Gateway (SPS) 12.8SP8 on RedHat 7;
    Adoptium JDK version 11.0.22+7;
  

Resolution

Upgrade or downgrade the JDK version to fix this issue;

To fix this crash, it's best to downgrade the JVM to the latest version of 1.8 since there haven't been any reports of this problem in Adoptium JDK 1.8.

Additional workaround to fix the crash : Set the minimum amount of memory allocated by the JVM equal to the maximum value (i.e, both -Xms and -Xmx to 4096m).