|
| Hello,
--[ First of all, please be kind enough not to shoot at me not to code long
pending requests... Make as if it were for education :-) ]--
I noticed a difference in behavior between WAS 4.0 / IHS 1.3 vs WAS 5.0 /
IHS 2.0, when dealing with a long pending request.
To illustrate, I made the following sleep.jsp:
<%!
static int staticcounter = 0;
%>
<%
int counter = ++staticcounter;
String msg = "sleep.jsp - Going to sleep - test #" + counter;
System.out.println(msg);
out.println(msg + "<br/>");
out.flush();
Thread.sleep(10 * 60 * 1000);
msg = "sleep.jsp - Awaken - test #" + counter;
System.out.println(msg);
out.println(msg + "<br/>");
%>
Running this page on WAS 4.0 / IHS 1.3 shows the "Going to sleep" message
for ten minutes, while the browser icon keeps moving, then the "Awaken"
message appears.
Running this page on WAS 5.0 / IHS 2.0 shows the "Going to sleep" message
for a few minutes, then the browser icon stops moving (transfer is
interrupted) and the "Awaken" message never appears because the transfer is
interrupted by the server-side (confirmed from a sniffer capture). StdOut
shows that the jsp reaches the end though, because the log contains the
"Awaken" message.
The question is:
* Did IHS, the IHS plug-in or WAS interrupt the connection ?
And the subsequent question is thus "Where is this timeout defined" ?
Thank you.
|
|