OPSS - Observing some Stuck Threads After Database Switchover on a failover environment
(Doc ID 2493789.1)
Last updated on MARCH 01, 2023
Applies to:
Oracle Platform Security for Java - Version 12.2.1.2.0 and laterInformation in this document applies to any platform.
Symptoms
Oracle-Label: OPSCS-12.2.1.2.0-161007.0818
After DB outage, and starting the DB switch over, in the fail-over environment, the system becomes slow and some stuck threads are observed on logs
#### ExecuteThread: '17' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "637" seconds working on the request "Workmanager: weblogic.kernel.Default, Version: 0, Scheduled=false, Started=true, Started time: 637545 ms
", which is more than the configured time (StuckThreadMaxTime) of "600" seconds in "server-failure-trigger". Stack trace:
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireShared(AbstractQueuedSynchronizer.java:967)
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireShared(AbstractQueuedSynchronizer.java:1283)
java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.lock(ReentrantReadWriteLock.java:727)
oracle.security.jps.az.common.util.JpsLock.lock(JpsLock.java:80)
oracle.security.jps.az.internal.runtime.service.PDPServiceImpl.getApplicationPolicy(PDPServiceImpl.java:951)
oracle.security.jps.az.internal.runtime.service.PDPServiceImpl.getApplicationPolicy(PDPServiceImpl.java:940)
oracle.security.jps.az.internal.runtime.service.PDPServiceImpl.getGlobalPolicy(PDPServiceImpl.java:911)
oracle.security.jps.az.internal.runtime.policy.ApplicationPolicyImpl.getGlobalPolicy(ApplicationPolicyImpl.java:360)
oracle.security.jps.az.internal.runtime.entitymanager.AppRoleManagerImplWrapper.getAllGrantedAppRoles(AppRoleManagerImplWrapper.java:109)
", which is more than the configured time (StuckThreadMaxTime) of "600" seconds in "server-failure-trigger". Stack trace:
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireShared(AbstractQueuedSynchronizer.java:967)
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireShared(AbstractQueuedSynchronizer.java:1283)
java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.lock(ReentrantReadWriteLock.java:727)
oracle.security.jps.az.common.util.JpsLock.lock(JpsLock.java:80)
oracle.security.jps.az.internal.runtime.service.PDPServiceImpl.getApplicationPolicy(PDPServiceImpl.java:951)
oracle.security.jps.az.internal.runtime.service.PDPServiceImpl.getApplicationPolicy(PDPServiceImpl.java:940)
oracle.security.jps.az.internal.runtime.service.PDPServiceImpl.getGlobalPolicy(PDPServiceImpl.java:911)
oracle.security.jps.az.internal.runtime.policy.ApplicationPolicyImpl.getGlobalPolicy(ApplicationPolicyImpl.java:360)
oracle.security.jps.az.internal.runtime.entitymanager.AppRoleManagerImplWrapper.getAllGrantedAppRoles(AppRoleManagerImplWrapper.java:109)
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |