OSM Datasource Suspended In One Server (Doc ID 2962636.1)

Last updated on JULY 20, 2023

Applies to:

Symptoms

On : 7.4.1.0.0 version, Performance

We are facing an issue in production environment concerning oms datasource in one server. The datasource went to suspended state and the following warning appeared in diagnostic logs.

Resuming the datasource did not worked as it went to suspend state again. Issue didn't appear after restarting the server.

ERROR
-----------------------
[2023-07-04T11:54:02.093+03:00] [XOSM_05] [WARNING] [] [com.mslv.oms.dataaccesslayer.AbstractProxy] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: oms-internal] [ecid: 2164f72c-5695-491f-9dbb-4b41ca7340b3-0000000a,0:4066:17309] [APP: oms] [partition-name: DOMAIN] [tenant-name: GLOBAL] SQL Exception Cannot obtain connection after 600 seconds. : weblogic.common.ResourceException: No good connections available. datasource osm_pool_rac2_group_a is suspended because At Tue Jul 04 11:50:34 EEST 2023 we got 0:weblogic.common.ResourceException: Could not create pool connection for datasource 'osm_pool_rac2_group_a'. The DBMS driver exception was: Interrupt task is already scheduled for the thread Thread[[ACTIVE] ExecuteThread: '37' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads] and the type SO_TIMEOUT[[

Changes

Cause

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