G1CMTask::make_reference_grey crash in SPS
search cancel

G1CMTask::make_reference_grey crash in SPS

book

Article ID: 370029

calendar_today

Updated On:

Products

SITEMINDER CA Single Sign On Secure Proxy Server (SiteMinder)

Issue/Introduction


Running CA Access Gateway (SPS) 12.8SP8CR01 with JDK 11.0.23+9, this one intermittently crashes and reports the following stack:

  #  SIGSEGV (0xb) at pc=0x00007fa6f19db8ca, pid=17669, tid=17687
  #
  # JRE version: OpenJDK Runtime Environment Temurin-11.0.23+9 (11.0.23+9) (build 11.0.23+9)
  # Java VM: OpenJDK 64-Bit Server VM Temurin-11.0.23+9 (11.0.23+9, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
  # Problematic frame:
  # V  [libjvm.so+0x7c08ca]  G1CMTask::make_reference_grey(oopDesc*)+0x2a

  Current thread (0x00007fa6b0002800):  GCTaskThread "GC Thread#2" [stack: 0x00007fa6b9bff000,0x00007fa6b9cff000] [id=17687]

  Stack: [0x00007fa6b9bff000,0x00007fa6b9cff000],  sp=0x00007fa6b9cfdc10,  free space=1019k
  Native frames: (J=compiled Java code, A=aot compiled Java code, j=interpreted, Vv=VM code, C=native code)
  V  [libjvm.so+0x7c08ca]  G1CMTask::make_reference_grey(oopDesc*)+0x2a
  V  [libjvm.so+0x7cf4ee]  G1CMSATBBufferClosure::do_buffer(void**, unsigned long)+0x3e
  V  [libjvm.so+0xd4b8b3]  SATBMarkQueue::apply_closure_and_empty(SATBBufferClosure*)+0x33
  V  [libjvm.so+0xedc6cd]  Threads::threads_do(ThreadClosure*)+0x4d
  V  [libjvm.so+0x7d0658]  G1CMRemarkTask::work(unsigned int)+0x168
  V  [libjvm.so+0xf7c9ed]  GangWorker::loop()+0x4d
  V  [libjvm.so+0xeded7f]  Thread::call_run()+0x14f
  V  [libjvm.so+0xc7d106]  thread_native_entry(Thread*)+0xe6

 

Cause


This is an issue in the Java code, not in the CA Access Gateway (SPS) code. The issue is outside CA Access Gateway (SPS).

The JVM stack reports that as well as the pkgcore script trace.

Searching the internet, other product seems to face very similar stack with other product using the JDK 11 too (1)(2).

It looks like to be limited to the JVM itself, around the Garbage Collector (GC).  No SPS related code is involved in the stack.
  

Resolution


Upgrade or downgrade the JVM to another version to fix the issue.

JDK 8 doesn't seem to be affected by these problems in the GC.

 

Additional Information