OVM Manager Web Page Shows Error 404--Not Found - weblogic.kernel.Default (self-tuning)' has been busy for "xxxxx" seconds (Doc ID 2324023.1)

Last updated on MAY 16, 2023

Applies to:

Goal

Errors seen in the AdminServer.log 

<2017-11-01T05:52:44.188-0400> <Error> <WebLogicServer> <[STUCK] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "xxxxx" seconds working on the request "Workmanager: default, Version: 0, Scheduled=true, Started=true, Started time: 17234019 ms
", which is more than the configured time (StuckThreadMaxTime) of "14,400" seconds in "server-failure-trigger". Stack trace:

<2017-11-01T02:51:19.434-0400> <Emergency> <odof.core.storage.RelationalStore> <Waiting for connection (210 of 720 tries)>
<2017-11-01T02:51:19.434-0400> <Emergency> <odof.core.storage.RelationalStore> <Waiting for connection (275 of 720 tries)>
<2017-11-01T02:51:19.435-0400> <Emergency> <odof.core.storage.RelationalStore> <Waiting for connection (273 of 720 tries)>

<2017-11-01T04:18:37.680-0400> <Error> <ovm.mgr.task.QueuedJobsTask> <Queued Jobs Task exception:
odof.exception.InternalException: Caught during invoke method: odof.exception.InternalException: Caught during acquire vessel: weblogic.jdbc.extensions.PoolLimitSQLException: weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool ovm-odof-ds to allocate to applications, please increase the size of the pool and retry..

Solution

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