unfortunately at the moment i don't know jdb
but can i try setting breakpoints
Amedeo
On 18/feb/2010, at 00.25, Mark Ritchie wrote:
> Hey!
>
> On 17/Feb/2010, at 1:53 PM, Mark Wardle wrote:
>> Might be worth checking it is the session you think it is?
>
> This is certainly something to consid
Hey!
On 17/Feb/2010, at 1:53 PM, Mark Wardle wrote:
> Might be worth checking it is the session you think it is?
This is certainly something to consider! Setting a break point on the session
constructor would be a quick way to show how many sessions are getting created
and when... Something
On 17/Feb/2010, at 2:46 AM, Amedeo Mantica wrote:
> 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
The last time I had session troubles, it turned out I had two sessions
as I managed to accidentally create an additional session with some
random session() call. I think this is v easy to do accidentally!
Might be worth checking it is the session you think it is?
I'm definitely not an expert
Nice looking site!
I am pretty sure that something else is going on. Maybe some code
calling terminate()? Some bad HTML causing a new session to get
created?
Chuck
On Feb 17, 2010, at 2:46 AM, Amedeo Mantica wrote:
Look at my website, www.confindustria.chieti.it, in the top right
co
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 wrot
Am 16.02.2010 um 22:21 schrieb Mark Ritchie:
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.
Well, he could override setTimeout in his WOSession subclass and set
the breakpoint there...
On 16/Feb/2010, at 1:21 PM, Mark Ritchie wrote:
> path/to/woa -NSJavaDebugging YES
>> stop in com.webobjects.appserver.WOSession.setTimeOut
>> run
>> ...
Dratted fancy e-mail readers change the greater then sign prompt into a
vertical bar... *grumble*
The above should be more like:
path
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.WO
no, is inside the R-R Loop
Amedeo
On 16/feb/2010, at 21.11, Timo Hoepfner wrote:
> To get the new timeout "applied", the session needs to be checked into the
> session store again. This usually happens at the end of the
> Request-Response-Loop. Any chance you modify the timeout outside of the
To get the new timeout "applied", the session needs to be checked into the
session store again. This usually happens at the end of the
Request-Response-Loop. Any chance you modify the timeout outside of the RR-loop?
Timo
Am 16.02.2010 um 20:54 schrieb Amedeo Mantica:
> no, i'm monitoring the v
may be in some undocumented method ?
On 16/feb/2010, at 20.56, Chuck Hill wrote:
>
> On Feb 16, 2010, at 11:54 AM, Amedeo Mantica wrote:
>
>> no, i'm monitoring the value it is 3600 after user logs in
>>
>> very strange
>>
>> there is a method that returns the remaining time ?
>
> No. Y
On Feb 16, 2010, at 11:54 AM, Amedeo Mantica wrote:
no, i'm monitoring the value it is 3600 after user logs in
very strange
there is a method that returns the remaining time ?
No. You could dig around in the WOSessionStore for it.
Chuck
On 16/feb/2010, at 20.16, Chuck Hill wrote:
no, i'm monitoring the value it is 3600 after user logs in
very strange
there is a method that returns the remaining time ?
Amedeo
On 16/feb/2010, at 20.16, Chuck Hill wrote:
>
> On Feb 16, 2010, at 8:24 AM, Amedeo Mantica wrote:
>
>> Hello,
>>
>> I have a strange behaviour,
>>
>> In m
On Feb 16, 2010, at 8:24 AM, Amedeo Mantica wrote:
Hello,
I have a strange behaviour,
In my application constructor i have:
setSessionTimeOut(600);
and it works perfectly, the session expires after 10 minutes
now, when an user authenticates i call this in session...
this.setTimeOut(3600);
Hello,
I have a strange behaviour,
In my application constructor i have:
setSessionTimeOut(600);
and it works perfectly, the session expires after 10 minutes
now, when an user authenticates i call this in session...
this.setTimeOut(3600);
but... the session still expire after 600 seconds...
16 matches
Mail list logo
