IBM Support

Workaround for TRANSPORT_WSI_DESERIALIZATION_ERROR or TRANSPORT_WSI_NETWORK_ERROR due to prematurely closed socket

Troubleshooting


Problem

When the Content Engine resides on WebSphere Application Server (any supported version) and you are using the CEWS transport, you might see an intermittent problem when exceptions are being returned to the client from the Content Engine server. (This problem does not occur with EJB transport.)

[{"Product":{"code":"SSNVNV","label":"FileNet Content Manager"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Content Engine","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"4.5.1","Edition":"All Editions","Line of Business":{"code":"LOB76","label":"Data Platform"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
28 April 2025

UID

swg21617408