My Oracle Support Banner

SAP Adapter Generates Stuck Threads (Doc ID 1356968.1)

Last updated on JANUARY 15, 2020

Applies to:

Oracle Service Bus - Version 10.3.1 and later
Information in this document applies to any platform.

Symptoms


SAP Adapter on OSB generates stuck threads, thus causing the weblogic server to go to "Warning" status, here is a sample of the stuck thread captured by weblogic:

<Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '13' for
queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "693"
seconds working on the request
"weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl@64d988",
which is more than the configured time (StuckThreadMaxTime) of "600" seconds.
Stack trace:
java.lang.Thread.sleep(Native Method)
com.ibi.sap.inbound.SapInboundAdapter$MasterThread.run(SapInboundAdapter.java:386)
com.iwaysoftware.afjca15.work.WorkImpl.run(WorkImpl.java:40)
weblogic.work.ContextWrap.run(ContextWrap.java:41)
weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

Changes

 

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
Changes
Cause
Solution


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