Hi Richard,

As I mentioned in this post, the reconnection caused by a content-length exhaustion is totally transparent to both the application and the user, and no status change at all happens.

If you observed a status change, this was just a coincidence, probably caused a network problem or by the client CPU saturation. The transition to STALLED state cannot be related to the content-length.

Do you have the detailed server-side logs showing the life-cycle of the user session that experimented the issue?