ALM Cash Flow Engine Process Fails With SIGSEGV Errors Due to More Than 200 Created Behavior Patterns (Doc ID 2129207.1)

Last updated on APRIL 22, 2016

Applies to:

Oracle Financial Services Asset Liability Management - Version 6.1.1 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Asset Liability Management (ALM)

Symptoms

On ALM 6.1.1, after creating more than 200 behavior patterns, any ALM process fails with the following errors when run from command line:

ERROR

# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00002ac34b258073, pid=5275, tid=47018369148560
#
# JRE version: 6.0_45-b06
# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.45-b01 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libaccess.so+0x24073] session::GetProcess(int)+0x13
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

--------------- T H R E A D ---------------

Current thread (0x000000001592a000): JavaThread "main" [_thread_in_native, id=5275, stack(0x00007fff617b8000,0x00007fff618b8000)]

siginfo:si_signo=SIGSEGV: si_errno=0, si_code=1 (SEGV_MAPERR), si_addr=0x0000000014b0f258

Registers:
RAX=0xffffffffffff0001, RBX=0x00000000ffff0001, RCX=0x00002aaaabe5eaa8, RDX=0xffffffffffdb0025

The ALM debug log ends abruptly while loading behavior patterns:

Module Logging OFS Access module data: select
select FSI_BEHAVIOUR_PATTERN_DETAIL.pattern_cd,
FSI_BEHAVIOUR_PATTERN_DETAIL.behaviour_sub_type_cd,
FSI_BEHAVIOUR_PATTERN_DETAIL.tenor,
FSI_BEHAVIOUR_PATTERN_DETAIL.multiplier,
FSI_BEHAVIOUR_PATTERN_DETAIL.percentage
from FSI_BEHAVIOUR_PATTERN_DETAIL
where FSI_BEHAVIOUR_PATTERN_DETAIL.pattern_cd = 90012.00000
order by FSI_BEHAVIOUR_PATTERN_DETAIL.tenor,
FSI_BEHAVIOUR_PATTERN_DETAIL.multiplier

If behavior patterns are deleted so that there are less than 200 behavior patterns, the problem resolves. As soon as additional behavior patterns are created, the ALM process again fails. It does not matter if the instrument records selected includes the new behavior patterns created.

The issue can be reproduced at will with the following steps:
1. Create more than 200 behavior patterns.
2. Run any ALM process.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms