Check your Kernel Recycling also I've attached a white paper from DSI
Symptoms
Following error message in the Dispatch kernel log when processing XML Interoperability requests via a third party application or using the XML APIs:
<errorReport code="11" state="3">
The network communication is broken.
Cause
The errors in the XML Dispatch kernel logs indicate that messages can not be sent to specific XML CO Kernel processes. There are only 2 possible causes why this error happens so watch for zombie callObject kernels:
1. The E1 Server was bounced, but the XML Interoperability clients talking to the server were not. This causes the clients to send requests with "stale" session ID's (i.e. to XML CO Kernel processes that no longer exist). The XML Interoperability client code should be smart enough to handle this situation and re-send the request with a blank Session ID so that a new one is created. If this is what's going on and the customer wants to avoid these errors, they should bounce the DSI clients when they bounce the E1 server.
Referring to a sample XML Dispatch log, it looks like the XMLDispatcher is trying to communicate with the COK with PID: 4492 at Mon Oct 22 07:34:53.727002. When checking the COK, It looks like the COK is already recycled at Mon Oct 22 01:00:04.914001. That means the COK 4492 is not longer available at the time when XMLDispatcher is trying to communicate. Hence, the following error gets generated in the XMLDispatcher logs. In this case the XML Interoperability client code should be smart enough to handle this situation and re-send the request with a blank Session ID so that a new one is created:
2776/2780 SYS:XMLDispatch Mon Oct 22 07:34:53.727000 Dispatcher.cpp714
Sending a message failed, netErr=17.
2776/2780 SYS:XMLDispatch Mon Oct 22 07:34:53.727001 Dispatcher.cpp714
ProcessDoc (processResquest): Dispatch Exception, state=2
2776/2780 SYS:XMLDispatch Mon Oct 22 07:34:53.727002 Dispatcher.cpp714
XMLDispatcher error report: <?xml version='1.0' encoding='utf-8' ?>
<jdeResponse environment="PD900" type="callmethod" user="dclink" session="4492.1350837271.3">
<errorReport code="11" state="3">
The network communication is broken.
</errorReport>
</jdeResponse>
The first part of the session ID is the Process ID of the XML CO Kernel. So, when the problem occurs, check the process ID to determine if if that process exists. If not, then this is what is causing the error.
2. The XML CO Kernels crashed. If this is the case, there would be zombie kernels in Server Manager. In this case additional research needs to be conducted by GSC to investigate why it crashed( became zombie kernel).
Solution
When getting this error, the recommendation for the 2 possible root causes is the following:
1. To correct the issue from happening again the XML Interop clients need to be restarted whenever the E1 servers are restarted or the corresponding COKs are recycled.
2. If there are callObject zombie kernels, submit the corresponding callObj and dispatch kernel logs from Enterprise Server to GSC for further analysis.