When I used jrun a while ago (ver 2.2a) it had an "undocumented" (found a post
about it on newsgroups, but it was absent from the documentation) time-out
value. It was set rather low (90 sec i think, it was a while ago). Changing it
from 90s to 500s did the trick.
There are actually 2 time-out values that you might be concerned with, since the
webserver itself can also decide to time-out. If you are using a browser as a
client, there may even be a third time-out value (5 min on most browsers???).
Anyways, I guess that those time-out settings are vendor specific. Sorry I can
not give a more concrete answer, but I thought it might help if I shared my
time-out experience with you. I do remember that this problem drove me crazy
before I solved it!
--shawn
Sean Snyders wrote:
>
> Hi,
>
> I'm programming quite an processing-intensive servlet and have a problem
> that
> it times-out on me. Can I send 'live' information back to the client while
> still in the
> "service" method of the servlet 'cause then I can tell the client I'm still
> processing
> the request, etc. and thus keeping the connection alive wihtout the timeout
> triggering on me.
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
