E1: XML: XML Dispatch Error Handling (Doc ID 660990.1)

Last updated on MAY 30, 2017

Applies to:

JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.

Symptoms

 
When the XML Dispatch receives a message addressed (via the session attribute in the XML document) to a specific kernel process, but that kernel process no longer exists; the error response document is not correctly sent back to the sender of the document. IE, response documents are not sent when an invalid session id is sent. The issue is that the message associated with the exception is not the correct one to send the response to.

The error messages in the jde.log would look the ones below. The two with the asterisk (*) in front of them are the ones indicating failure to send the response message to the sender:

836/4044 SYS:XMLDispatch Sun Feb 03
08:57:49.351000 Dispatcher.cpp603
Sending a message failed.

836/4044 SYS:XMLDispatch Sun Feb 03
08:57:49.351001 Dispatcher.cpp603

XMLDispatcher error report: <?xml version='1.0'
encoding='utf-8' ?>
<jdeResponse environment="PD812" type="callmethod" user="DSI
" session="5348.1202041964.1">
<errorReport code="11" state="3">
The network communication is broken.
</errorReport>
</jdeResponse>

*836/4044 SYS:XMLDispatch Sun Feb
03 08:57:49.351002 Dispatcher.cpp603
Sending a message failed.

*836/4044 SYS:XMLDispatch Sun Feb
03 08:57:49.351003 Dispatcher.cpp603
Cannot send the error report.
836/4044 SYS:XMLDispatch Sun Feb 03
08:57:49.351004 Dispatcher.cpp603
ProcessDoc: Dispatch Exception

STEPS TO REPLICATE AND TEST

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