Scheduler Takes Too Long To Startup/Stabilize Due To TPW Error 'All Universal Connection Pool connections are in use'
(Doc ID 2089389.1)
Last updated on DECEMBER 04, 2019
Applies to:Oracle Utilities Mobile Workforce Management - Version 2.1.0 and later
Oracle Real-Time Scheduler - Version 2.1.0 and later
Information in this document applies to any platform.
**Examples provided in this article do not represent real life personal/confidential information**
**Disclaimer:** This KM article may include the following abbreviations:
MWM - Oracle Utilities Mobile Workforce Management
ORTS/ORS/ERTS - Oracle Real-Time Scheduler
TPW - Threadpoolworker
UCP - Universal Connection Pool
On MWM v2.2
MWM: scheduler takes too long to stabilize
While testing MWM 2.2, a specific scheduler (SCHED1), which handles 10K tasks and is not the biggest scheduler, takes too long to startup and stabilize. It can take as long as 1 hout for the scheduler to become 'green' in Batch Control Global View and after 90 minutes of execution, 'update schedule' entries are still not logged in the stdout log.
Other schedulers in the environment are taking 30 minutes for stabilizing.
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