Pipeline Core In Production Environment: "Attempt To Exit Due To Signal Caught: Sigbus"
Last updated on MAY 15, 2012
Applies to:Oracle Communications Billing and Revenue Management - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 7.3.1 to 7.4.0]
Information in this document applies to any platform.
Updated with V7.4 info on 15-May-2012
* In a customers production box, core dumps were frequently observed and the pipeline framework would go down printing the following message(s) on the console :
Attempt to exit due to signal caught: SIGBUS
Assertion failed: sizeclass < SIZE_CLASSES, file hoardheap.h, line 395
* Customer would process the below semaphores for call assembling module and the core dump would happen :
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.
* Two sample stack trace files are attached, one for the core from Dat_BalanceBatch module and another from call_assembling module, for reference.
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