OSB Managed Server Going To Unknown State And Not Accepting Any Connections Requires Restart (Doc ID 2796628.1)

Last updated on AUGUST 12, 2024

Applies to:

Symptoms

On : NA version, Core SOA Product Issues

Issue:
------
SOA Cloud servers going into unknown state and not accepting any requests and requires restart for the server to process any requests.

Thread dump shows the weblogic workmanager thread stuck on below stack:

"Timer-2" #25 daemon prio=5 os_prio=0 tid=0x00007fb914b8f800 nid=0x7069 waiting for monitor entry [0x00007fb9033fe000]
java.lang.Thread.State: BLOCKED (on object monitor)
at weblogic.work.RequestManager.purgeHogs(RequestManager.java:1304)
- waiting to lock <0x00000005c2c141f8> (a java.util.ArrayList)
at weblogic.work.IncrementAdvisor.evaluateThreadCount(IncrementAdvisor.java:361)
at weblogic.work.IncrementAdvisor.run(IncrementAdvisor.java:283)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)

Expected Behavior:
------------------
Server should not go to unknown state and should process requests.

Steps to Reproduce:
-------------------
- Issue specific to environments suddenly stopped accepting requests.

Cause

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