WebSphere buffering servlet output?

Hi WebSphere knowledgeables,

We have a servlet that performs lengthy actions, all the while sending output
back to the browser (What it really does is serve as a relay between an applet
on the browser and a backend server).

This servlet runs properly on all servlet engines we tested or deployed it on,
including non-AS/400 WebSphere, and the output (which is constantly flushed)
gets to the browser in a timely manner.

What we're seeing when the servlet runs on the AS/400 WebSphere, is that the
output is buffered in WebSphere, and only gets to the client when the output is
closed.  This causes the applet on the client to time out while waiting for
replies, eventually breaking the whole setup.  This behaviour has been verified
with a simple test servlet that runs a loop of "wait 5 sec., print a line".  If
you run this test servlet on any other platform you get a new line every 5
seconds.  If you run it on the AS/400 WebSphere you get a long delay (until the
servlet ends) and then you get the whole output at once.

Does anyone know if there's any way we can convince WebSphere to pass the
servlet output through without buffering it?

Thanks in advance,

Nimrod


+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---