|
| Hello,
We have found a strange bug/feature in Websphere that we never
experienced when using Tomcat. A little foreknowledge, We are running
WebSphere 5.1 on Win2000. Our application is a Servlet/Applet.
Our servlet, as you may have guessed, handles a large number of
requests coming from the applet. Some of the requests do not require
a response. If we do not provide a response to the Applet, our applet
hangs for about 5 seconds when pulling information from the
InputStreamReader. Upon further examination I also realized that if I
send I send a blank stream via the Text/HTML mimeType we have the
exact same problem.
Now, of course there is a simple patch. I make sure to always send
something and check all Text/HTML streams and make sure they are never
null or blank. However, this is more a patch than a solution. A
solution would be to determine why WebSphere does this. It seems to
me that WebSphere sits and waits for the stream, and when it doesn't
receive one after 5 seconds it continues. Is there a way to actually
fix this? Has anyone else experienced this problem before?
Please let me know
Dan
|
|