I have been working on an issue where for certain users the download would just not complete.
The issue started after we had upgraded our application server.
While Debugging further we identified a common pattern the download would error out ~ 60 Seconds..
After a bit of research we identified that this was related to Complete Message Timeout on Weblogic Server.
That is if we increase the value to above 200 and if we have a slow connection and a large file size the download would stop ~ 200 Seconds.
And the Maximum limit for the same is 480 seconds.
This is what the official document says about Complete Message Timeout.
The maximum number of seconds that this server waits for a complete message to be received. If you configure network channels for this server, each channel can override this message timeout.
This timeout helps guard against a denial of service attack in which a caller indicates that it will be sending a message of a certain size which it never finishes sending.
MBean Attribute:
ServerMBean.
Minimum value: 0
Maximum value: 480
If I remember correctly we could set -1 for earlier versions of weblogic so that we disable the limit.
I can understand a limit on the Request to guard against DOS Attacks but why limit the Response time.
To Summarize we can apply the patch for Bug:13263584 and use the below flag
-Dweblogic.
