I may have a similar problem. See my message from
yesterday:
"connectionTimeout and disableUploadTimeout"

Assuming you've got something like this in web.xml:

<session-config>
  <session-timeout>360</session-timeout>
</session-config>

that should take care of your session (the above
allows for a 6 hour session).

However, there appears to be a separate 'connection
timeout' or 'request timeout' concept which will
prevent a long request's results from ever displaying.
60 minutes seems to be the limit, but I haven't
pinned this down.

I've tried using 'connectionTimeout' and
'disableUploadTimeout' but neither seems to have any
effect.

Sorry to answer your question with a question, but
maybe we can pursue this together.

-Rob


--- "Altug B. Altintas" <altuga@(protected):
> Hi
> We have got a page which process a request for a
> long time (because of algoritm) so we set
> "session-timeout = 1000" in web.xml
> but if the user request this page, it starts to
> process and then after a time (~30 min) browser
> gives "page cannot be displayed" but the request is
> still be processed in server so the user cannot see
> anything. Which parameter can i set to solve this
> problem.
>
> Regards
> Altug


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!
http://webhosting.yahoo.com/ps/sb/

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)