Re: session timeout trouble
Re: session timeout trouble
- Subject: Re: session timeout trouble
- From: Amedeo Mantica <email@hidden>
- Date: Wed, 17 Feb 2010 11:46:49 +0100
Look at my website, www.confindustria.chieti.it, in the top right corner there is a barely visible number indicating the session timeout value... ( 1200 ), after user log in, the value go to 3600 and remain 3600, but session expires after 1200
Amedeo
On 16/feb/2010, at 22.21, Mark Ritchie wrote:
> On 16/Feb/2010, at 12:13 PM, Amedeo Mantica wrote:
>> no, is inside the R-R Loop
>
>
> Hey Amedeo!
>
> I would set a breakpoint on the setTimeOut() method and see when the timeout is being set!
> Using jdb, this would be something like:
>
> path/to/woa -NSJavaDebugging YES
>> stop in com.webobjects.appserver.WOSession.setTimeOut
>> run
>> ...
> Breakpoint hit: "thread=WorkerThread0", com.webobjects.appserver.WOSession.setTimeOut(), line=678 bci=0
>
>> where
> [1] com.webobjects.appserver.WOSession.setTimeOut (WOSession.java:678)
> [2] com.webobjects.appserver.WOSession.<init> (WOSession.java:233)
> ...
>
>> cont
>
> Repeat until you find the case where the timeOut is getting set. ;-)
> Note that the first time is the WOSession constructor setting the initial value.
> It's the times after that are most interesting!
> M.
>
> P.S. I'm open to learning how to do this in Eclipse however my understand is that Eclipse can't set break points when it doesn't have the source code.
>
_______________________________________________
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