My Oracle Support Banner

Pipeline Core In Production Environment: "Attempt To Exit Due To Signal Caught: Sigbus" (Doc ID 1212439.1)

Last updated on FEBRUARY 21, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 to 7.4.0.0.0 [Release 7.3.0 to 7.4.0]
Information in this document applies to any platform.

Symptoms

*  In a production environment, core dumps were frequently observed and the pipeline framework would go down printing the following messages on the console :

Attempt to exit due to signal caught: SIGBUS
or
Assertion failed: sizeclass < SIZE_CLASSES, file hoardheap.h, line 395

*  User would process the below semaphores for call assembling module and the core dump would happen :

ifw.Pipelines.GSM.Functions.Processing1.FunctionPool.CallAssembling.Module.FlushLimit=1
ifw.Pipelines.GSM.Functions.Processing1.FunctionPool.CallAssembling.Module.KeepCallOpen = True


*  Even otherwise, core dump would happen while rating CDRs in production, especially while running billing in parallel, leading to some locks on the balance groups.


*  Sample stack trace for the core from Dat_BalanceBatch module:

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.