My Oracle Support Banner

WorkListener.workCompleted API is never called in weblogic 10.3.0 and 10.3.1 (Doc ID 1439145.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle Weblogic Server - Version 10.3 and later
Information in this document applies to any platform.


Migration from WebLogic Server 9.2 MP2 to Weblogic 10.3.0 is failing with no change to the application code.

Thread dump analysis shows the following stuck thread:

"[STUCK] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=3 tid=0x0343d400 nid=0x20 in Object.wait() [0x990ff000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0xe71c1bb8> (a$Callback)
- locked <0xe71c1bb8> (a$Callback)
at com.mycompany.ExaminWorkManagerBean.scheduleWork(
at com.mycompany.ExaminWorkManagerBean.startNewBatch(
at com.mycompany.ExaminWorkManager_awk6cw_EOImpl.startNewBatch(
at com.mycompany.ExaminWorkManager_awk6cw_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(
at weblogic.rmi.cluster.ClusterableServerRef.invoke(
at weblogic.rmi.internal.BasicServerRef$
at Source)
at weblogic.rmi.internal.BasicServerRef.handleRequest(

The method waitForAll() is waiting for ever, work is neither marked as completed nor the callback is happening.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

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