OneClick JRE Thick Client constantly crashes in Spectrum 24.3.5 and higher

Products

• Network Observability
• Spectrum

Issue/Introduction

After we have upgraded to Spectrum 24.3.5 and later 24.3.9, we noticed that all of our JRE Thick client users were experiencing random crashes.

When we check on the OneClick server, we can see that a hs_err_pid####.log file was created at the time of the crash.

 

The hs_err_pid####.log file has the crash similar to this

 

Current thread (0x0000029f1960fad0):  JavaThread "AWT-Windows" daemon [_thread_in_native, id=14696, stack(0x000000dd2dc00000,0x000000dd2dd00000)]

Stack: [0x000000dd2dc00000,0x000000dd2dd00000],  sp=0x000000dd2dcfea00,  free space=1018k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  [awt.dll+0xdc8a1]

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j  sun.awt.windows.WToolkit.eventLoop()V+0 [email protected]
j  sun.awt.windows.WToolkit.run()V+50 [email protected]
j  java.lang.Thread.run()V+11 [email protected]
v  ~StubRoutines::call_stub

siginfo: EXCEPTION_ACCESS_VIOLATION (0xc0000005), reading address 0x0000000000000008

Environment

Spectrum 24.3.5 and higher

OneClick JRE Thick client

 

Problem is seen on JRE 17.0.12 (on Spectrum 24.3.5) and now 17.0.14 (Spectrum 24.3.9).

 

Cause

JDK bug seems similar to what is reported here

 

JDK Crash Bug

 

Resolution

Upgrade Client JDK to OpenJDK Java 17.0.16 which we ship in 25.4.1.

 

Then from OneClick Admin page, OneClick Client Configuration, under supported JRE version,  click the option to "Allow New Versions" while hi-lighting your current version, this will allow OneClick to use the 17.0.16 from the OneClick Client.

 

 

Additional Information

For more information about using higher JRE versions in OneClick Spectrum you can see it here