ThreadPoolWorker Not Performing Garbage Collection
Last updated on AUGUST 07, 2017
Applies to:Oracle Utilities Customer Care and Billing - Version 2.3.1 to 2.3.1 [Release 2.3]
Oracle Utilities Framework - Version 2.2.0 to 2.2.0 [Release 2.2]
Oracle Utilities Customer Care and Billing Integration to Oracle Utilities Meter Data Management - Version 3.1.1 to 3.1.1 [Release 3.1]
Information in this document applies to any platform.
With CCB 2.3.1 SP5 and Framework 2.2.0 SP15, F1-SYNRQ ("Sync Request Monitor Process") is suffering a performance degradation that continues to get worse as the job continues. If left running long enough, all threads will crash with outOfMemory excpetions at whatever point in the code that thread was executing.
F1-SYNRQ is based on com.splwg.base.domain.common.businessObject.batch.AutoTransitionBatchProcess, so any batch job that uses this entry point could suffer the same issue.
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