My Oracle Support Banner

Stuck Thead On Admin Server (Doc ID 1460242.1)

Last updated on AUGUST 18, 2017

Applies to:

Oracle Communications Order and Service Management - Version 7.0.3 and later
Information in this document applies to any platform.


When starting up the Admin Server everything is fine. Once I start an OSM managed server via the Node Manager shortly after OSM is started, the Admin Server gets a stuck thread warning.
OSM still functions fine.

"[STUCK] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=3 tid=0x017b1400 nid=0x1c runnable [0x3917e000] java.lang.Thread.State: RUNNABLE at Method) at at sun.nio.cs.StreamDecoder.readBytes( at sun.nio.cs.StreamDecoder.implRead( at - locked <
0xf7c4cc18> (a at at at - locked <
0xf7c4cc18> (a at at weblogic.nodemanager.client.NMServerClient.checkResponse( at weblogic.nodemanager.client.NMServerClient.checkResponse( at weblogic.nodemanager.client.NMServerClient.start( - locked <
0xf7c4c978> (a weblogic.nodemanager.client.PlainClient) at weblogic.nodemanager.mbean.StartRequest.start( at weblogic.nodemanager.mbean.StartRequest.execute( at weblogic.kernel.WorkManagerWrapper$ at at


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

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