Never mind folks. I was using in a debugger and was looking caucho
session's _maxInactiveInterval, which was in millis, but the return
value of getMaxInterval was indeed in seconds, as expected. 

My bad, sorry for the false alarm.

----- Original message -----
From: "L Logue" <[EMAIL PROTECTED]>
To: resin-interest@caucho.com
Date: Wed, 03 Jan 2007 13:18:45 -0500
Subject: Re: 3.0.22: session.maxInactiveInterval in milliseconds

> Date: Wed, 3 Jan 2007 09:06:49 -0800
> From: Scott Ferguson <[EMAIL PROTECTED]>
>
> On Jan 3, 2007, at 7:23 AM, L Logue wrote:
>
>> The 1.4 EE API specified that maxInactiveInterval is "an integer
>> specifying the number of seconds this session remains open between
>> client requests."  In my development resin conf , when I set the
>> session-timeout configuration to 1 minute, session.maxInactiveInterval
>> came out as 60000, but it should be 60 instead.
>
> In what context are you seeing the 60000?  JMX?  The JMX value is in  
> milliseconds like the other JMX time values.

In the web-app context. I registered an HttpSessionListener, and in 
sessionCreated(): httpSessionEvent.getSession().getMaxInactiveInterval()
was 60000.

Thanks.

_______________________________________________
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest

Reply via email to