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 126.96.36.199.0 to 188.8.131.52.0 [Release 7.3.0 to 7.4.0]
Information in this document applies to any platform.
* 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
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.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:
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