My Oracle Support Banner

WLS 12.2.1.3 Deadlock In PolicyManager When Managed Server Starts Up (Doc ID 2530753.1)

Last updated on AUGUST 06, 2020

Applies to:

Oracle Web Services Manager - Version 12.2.1.3.0 and later
Information in this document applies to any platform.

Symptoms

On WebLogic Server 12.2.1.3, a deadlock occurs in the OWSM Policy Manager when a managed server starts up.
Some of the managed servers of a domain don't start at all, however, the majority of the managed servers do start fine.

Thread dumps of the failing server presenting a deadlock in the policy manager:

<Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: 'X' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "640" seconds working on the request "Workmanager: weblogic.kernel.Default, Version: 0, Scheduled=false, Started=true, Started time: <MILLISECONDS> ms", which is more than the configured time (StuckThreadMaxTime) of "600" seconds in "server-failure-trigger". Stack trace:
oracle.j2ee.ws.client.mgmt.runtime.SuperClientInterceptorPipeline.createSOAPBindingInterceptorChain(SuperClientInterceptorPipeline.java:257)
oracle.j2ee.ws.client.mgmt.runtime.SuperClientInterceptorPipeline.getPolicyPipeline(SuperClientInterceptorPipeline.java:327)
......

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


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