Platform: Csla 3.8.4, Winforms Smart Client, WCF DataPortal
We have an business object that contains the binary data for a file as one of its properties. It is implemented as a byte array.
Larger files > 2MB are having issues saving. We receive a 404 error. After tracking the issue, IIS has nothing in its error logs, but HTTP.sys logs show POST Connection_Dropped entries.
After googling a bit, it appears that these entries are typically the result of a client closing the HTTP connection prior to the servers response.
Has anyone else experienced the same issue?
If I want to see if the client is actually closing the connection, where in CSLA code would be a good place to start?
I know Microsoft suggests using streaming for larger files (sadly they don't define the term larger, or at least I can't find it). CSLA does not support streaming, so it is not an option for us. In addition, the actual file traffic will be minimal, and we have very powerful server hardware.
First, try enabling Tracing in web.config on the WcfHost. The resulting log file should include more information on any exceptions that cause the connection to be closed.
Copyright (c) Marimer LLC