关于 FileNet P8 4.5.1 TRANSPORT_WSI_SERIALIZATION_ERROR 解决

 

When the Content Engine resides on WebSphere Application Server (any supported version) and you are using 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.) In these cases, the socket for the

HTTP response is prematurely closed. Depending on the exact timing of the packets

arriving at the client side, this can result in an EngineRuntimeException with any of

these ExceptionCode values: TRANSPORT_WSI_DESERIALIZATION_ERROR or

TRANSPORT_WSI_NETWORK_ERROR. The underlying root cause exception will

be an instance of java.io.IOException.

Workaround: Change the HTTP response used by the Content Engine server when it

is returning an exception. A different response code will be used if you set this Java

system property in the JRE of the Content Engine server:

FileNet.WSI.HttpFaultResponseCode. A value of 599 is recommended (the default

value is 500). You would typically set this value via the WebSphere administrative

console in the JVM parameters screen: -

DFileNet.WSI.HttpFaultResponseCode=599