SAS® OnDemand Decision Engine stops responding or the Java Virtual Machine (JVM) crashes with a signal segmentation violation (SIGSEGV)


If you use the REST API to update an analyst list while transactions are being processed, SAS OnDemand Decision Engine might stop responding, or the JVM might crash. Transactions will no longer be processed until you restart SAS OnDemand Decision Engine.

If SAS OnDemandDecision Engine stops responding to incoming transactions, messages similar to the following occur in the log:

2025-05-27T15:24:43,439 [RMI TCP Connection(4)-10.21.14.39] ERROR SharedMemorySAS SAS channel [pid=443361 key=5024] is not responding, closing

2025-05-27T15:24:43,440 [RMI TCP Connection(4)-10.21.14.39] DEBUG SASSharedMemoryChannel [pid=443361 key=5024] closing

2025-05-27T15:24:43,440 [RMI TCP Connection(4)-10.21.14.39] INFO  SASSharedMemoryChannel [pid=443361 key=5024] closed

2025-05-27T15:24:43,458 [Engine  0] DEBUG SASSharedMemoryChannel [pid=443361 key=5024] closing

2025-05-27T15:24:43,458 [Engine  0] DEBUG SASSharedMemoryChannel kill -SIGKILL 443361

…

2025-05-27T15:24:43,806 [Engine  3] WARN  TRANSACTION_FAILED elapsed=24.0ms cmx_tran_id=0032191090672464 smh_acct_type="CS" smh_activity_type="MC" smh_rtn_code="12" smh_reason_code="ERRR"

com.sas.finance.fraud.engine.sas.SharedMemorySAS$ChannelWaitTimeout: 20ms passed waiting for a SAS channel

If the JVM crashes, the log contain the following messages:

#

# A fatal error has been detected by the Java Runtime Environment:

#

#  SIGSEGV (0xb) at pc=0x000014b88dafa2c5, pid=420760, tid=420818

#

# JRE version: OpenJDK Runtime Environment Zulu11.56+20-SA (11.0.15+10) (build 11.0.15+10-LTS)

# Java VM: OpenJDK 64-Bit Server VM Zulu11.56+20-SA (11.0.15+10-LTS, mixed mode, tiered, compressed oops, concurrent mark sweep gc, linux-amd64)

# Problematic frame:

# v  ~StubRoutines::jshort_disjoint_arraycopy

#

# Core dump will be written. Default location: Core dumps may be processed with "/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h %e" (or dumping to
/sasvol01/confighome94/Lev1/Applications/SASFraudManagement/6.2/SAMS/engine/
Server1/logs/core.420760)

#

# An error report file with more information is saved as:

#
/sasvol01/confighome94/Lev1/Applications/SASFraudManagement/6.2/SAMS/engine/
Server1/logs/hs_err_pid420760.log

…