Incident Creation Fails with the Error "DIA-48415: Syntax error " for Some Stuck Thread Conditions (Doc ID 2221316.1)

Last updated on JANUARY 12, 2017

Applies to:

Oracle Fusion Middleware - Version 12.2.1.0.0 and later
Information in this document applies to any platform.

Symptoms

In 12.2.1 environment, managed server cannot create the needed incident files during certain stuck thread scenarios.

Below is the snippet of a successful log entry 

<Dec 9, 2015 7:17:56 AM PST> <Emergency> <oracle.dfw.incident> <BEA-000000> <incident 8 created with problem key "BEA-000337 [/oraclediagent/invoke.do]"> 

For unsuccessful attempt, the following error is seen when creating incident files which points to the syntax error in the "POST" string:

<Mar 11, 2016 11:55:04 AM PST> <Warning> <oracle.dfw.framework> <DFW-40121> <failure creating incident from WLDF notification oracle.dfw.incident.IncidentCreationException: DFW-40116: failure creating incident Cause: DFW-40112: There was an error executing adrci commands; the following errors have been found "Inound in string [create incident problem_key="BEA-000337 [/oraclediagent/invoke.do]",]" error_facility] at column [85].

 
For the incident errors that DO create incident directories, the Watch Rule details look like this:

<Watch "StuckThread" in module "Module-FMWDFW" with severity "Notice" on server "odi_server1" has triggered at May 13, 2016 11:39:51 AM PDT. Notification details: WatchRuleType: Log WatchRule: (SEVERITY = 'Error') AND ((MSGID = 'WL-000337') OR (MSGID = 'BEA-000337')) WatchData: MESSAGE = [STUCK] ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "610" seconds working on the request "javax.management.remote.rmi.RMIConnectionImpl", which .
is more than the configured time (StuckThreadMaxTime) of "600" seconds in "server-failure-trigger". Stack trace:


For the incident errors that do NOT create incident directories, the Watch Rule details look like this:

<Watch "StuckThread" in module "Module-FMWDFW" with severity "Notice" on server "odi_server1" has triggered at May 25, 2016 11:05:17 AM PDT. Notification details: WatchRuleType: Log WatchRule: (SEVERITY = 'Error') AND ((MSGID = 'WL-000337') OR (MSGID = 'BEA-000337')) WatchData: MESSAGE = OdiDMTarget-153944850-10-0 has been busy for "654" seconds working on the request "Http Request Information: weblogic.servlet.internal.ServletRequestImpl@558537d7[POST
/oraclediagent/invoke.do] ", which is more than the configured time (StuckThreadMaxTime) of "600" seconds in "server-failure-trigger". Stack trace:

 

 

Cause

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 hundreds of Community platforms