Christopher Schultz wrote:
This was already pointed out (by me, in fact). Sometimes, you can trick
the browser into keeping the connection open by sending data back little
by little. For instance, I think you might be able to keep the
connection open by sending HTML comments like "" every so ofte
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bryan,
Bryan Basham wrote:
> Did you know that you have programmatic control over the
> session timeout[?] Simply call the setMaxInactiveInterval method
> on the HttpSession object with a value in seconds.
This is the method the OP is already using,
Did you know that you have programmatic control over the
session timeout. Simply call the setMaxInactiveInterval method
on the HttpSession object with a value in seconds. So if you
know that a given request will take 10 minutes you can say:
session.setMaxInactiveInterval(600); at the beginning o
Hi 'Christopher Schultz,
I'm sorry for late reply, i was away from work.
Yes, setting session timeout -1 didn't work.
We are using TC 5.0.16.
I will check with TC 5.5 as you suggested.
Christopher Schultz-2 wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Muneen
Hi Nehoff,
I'm sorry for late reply, i was away from work.
I can not modify the session timeout at web.xml because this modification is
effects comeplete application but i need long session only at one or two
places
JNeuhoff wrote:
>
> Have you inserted this into your web.xml?
>
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Muneendra,
Muneendra wrote:
> Lets says, my Web Application session timeout period is 5 minutes.
> I made a Http request to server and corresponding Servlet requires more than
> 5 minutes lets say 10 minutes to complete the business logic.
Your brows
Have you inserted this into your web.xml?
10
Muneendra wrote:
>
> Hi,
> I have a little complicated issue with HttpSession timeout process. It
> goes like this.
>
> Lets says, my Web Application session timeout period is 5 minutes.
> I made a Http request to s
