E1: XML: Getting "jdeXMLResponse receive failed" error message on third party when processing XML documents via XML Interoperability. (Doc ID 888536.1)

Last updated on DECEMBER 27, 2022

Applies to:

Symptoms

Experiencing XML Interop issues when processing DcLink XML documents and occassionally, the submission results in a "jdeXMLResponse receive failed" error message on DSI side. The callObject kernel is logging below errors, but the transaction on the E1 side is completing successfully. DSI does not get a successful XML response document to acknowledge completion.

18338/1 MAIN_THREAD Mon Aug 10
06:52:46.189942 netflow.c880
18338 (pid) in routeOutgoingQueue(), unable to send message: sd=13, msgId=1, msgHost=<IP>, msgPort=6014, sendingHost=<IP>, msgType=13513, msgRange=21, krnlName=XML DISPATCH KERNEL, reqNet=4416, resNet=18338, reqKrnl=4416, resKrnl=18320, msgFlags=0.

This is the XML message type that DSI sends to E1 and E1 sends back. All of these errors occur AFTER failing to send messages to the RTE transaction server:

18338/1 MAIN_THREAD Mon Aug 10
06:52:46.189444 netflow.c880
18338 (pid) in routeOutgoingQueue(), unable to send message: sd=-1, msgId=180, msgHost=<IP>, msgPort=9284, sendingHost=<IP>, msgType=15501, msgRange=28, krnlName=APP SERVER KERNEL, reqNet=0, resNet=0, reqKrnl=2375, resKrnl=0, msgFlags=0.

Cause

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