Patch 28507258 For SOA 126.96.36.199.180417
(Doc ID 2503630.1)
Last updated on JANUARY 08, 2020
Applies to:Oracle SOA Suite - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
Occasionally the BPM servers go into the WARNING state with the following stuck trace:
<Watch "StuckThread" in module "Module-FMWDFW" with severity "Notice" on server "WLS-BPM-14" has triggered at Jan 11, 2019 11:52:23 AM CET. Notification details:
WatchRule: (SEVERITY = 'Error') AND ((MSGID = 'WL-000337') OR (MSGID = 'BEA-000337'))
WatchData: DATE = Jan 11, 2019 11:52:23 AM CET SERVER = WLS-BPM-14 MESSAGE = [STUCK] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "644" seconds working on the request "oracle.soa.management.internal.ejb.impl.FacadeFinderBean_4vacyo_FacadeFinderBeanImpl", which is more than the configured time (StuckThreadMaxTime) of "600" seconds in "server-failure-trigger". Stack trace:
You found the following Knowledge article that describes an identical situation and suggests to apply the <Patch 28507258>:
SOA 184.108.40.206: StuckThreads When Getting AuditTrails Using ExecuteDumps (Doc ID 2483445.1)
<Bug 28507258> : StuckThreads when getting AuditTrails using executeDumps
The patch referenced is for SOA 220.127.116.11.180703 but you require a fix for SOA 18.104.22.168.180417.
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