Re: Session timeout in debgugger
Re: Session timeout in debgugger
- Subject: Re: Session timeout in debgugger
- From: Chuck Hill <email@hidden>
- Date: Wed, 1 Dec 2004 12:33:24 -0800
The session timeout only affects the length of time that an idle
session will live. The timeout you are seeing are between the
woadaptor and your app. There relevant settings are labeled Connect
Timeout and Send Timeout in JavaMonitor. You will want to avoid
setting this too high (900 seconds is too high) in deployment to avoid
adversing affecting things when a problem happens. Sometimes a timeout
is a good thing!
Chuck
On Dec 1, 2004, at 9:41 AM, Erwin wrote:
I have a session timeout in my woapp
Using a 900.0 seconds timeout.
[2004-12-01 17:49:30 CET] <main> Opening application's URL in browser
I running mode, no problem I tested it,
but in debugging mode, I get a "no instance available" after less than
1 minute...
why not 900 sec ?
Erwin _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
village.net
This email sent to email@hidden
--
Practical WebObjects - a book for intermediate WebObjects developers
who want to increase their overall knowledge of WebObjects, or those
who are trying to solve specific application development problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden