WorkListener.workCompleted API is never called in weblogic 10.3.0 and 10.3.1
(Doc ID 1439145.1)
Last updated on FEBRUARY 03, 2019
Applies to:
Oracle Weblogic Server - Version 10.3 and laterInformation in this document applies to any platform.
Symptoms
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 weblogic.work.commonj.CommonjWorkManagerImpl$Callback)
at weblogic.work.commonj.CommonjWorkManagerImpl$Callback.waitForAll(CommonjWorkManagerImpl.java:131)
- locked <0xe71c1bb8> (a weblogic.work.commonj.CommonjWorkManagerImpl$Callback)
at weblogic.work.commonj.CommonjWorkManagerImpl.waitForAll(CommonjWorkManagerImpl.java:72)
at com.mycompany.ExaminWorkManagerBean.scheduleWork(ExaminWorkManagerBean.java:189)
at com.mycompany.ExaminWorkManagerBean.startNewBatch(ExaminWorkManagerBean.java:143)
at com.mycompany.ExaminWorkManager_awk6cw_EOImpl.startNewBatch(ExaminWorkManager_awk6cw_EOImpl.java:132)
at com.mycompany.ExaminWorkManager_awk6cw_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
The method waitForAll() is waiting for ever, work is neither marked as completed nor the callback is happening.
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 |