[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jetty-users] Jetty clustering not working properly (jettySessions expiryTime getting set to 0 after sometime)
|
Venkat,
Thanks for the clear explanation, I raised this bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=380866
Will let you know when its fixed.
Jan
On 29 May 2012 07:59, venkat_99 <venkaiahp@xxxxxxxxx> wrote:
> Here is the config of JDBCSessionManager we are using on both the nodes
>
> <Configure class="org.eclipse.jetty.webapp.WebAppContext">
> <Get name="server">
> <Get id="jdbcIdMgr" name="sessionIdManager"/>
> </Get>
> <Set name="sessionHandler">
> <New class="org.eclipse.jetty.server.session.SessionHandler">
> <Arg>
> <New
> class="org.eclipse.jetty.server.session.JDBCSessionManager">
> <Set name="idManager">
> <Ref id="jdbcIdMgr"/>
> </Set>
> <Set name="SaveInterval" type="long">-60000</Set>
> <Set name="MaxInactiveInterval" type="int">120</Set>
> </New>
> </Arg>
> </New>
> </Set>
> </Configure>
>
> The JDBCSessionIdManager is defined separately in the config file of
> jetty-7.xml, in our case both the nodes have the maxIdleTime. When I
> inspected into the methods of access during session migration whenever a
> session migration happens from one node to other nodes the second
> constructor of AbstractSession is being called. In this constructor there is
> no set like below on the session, due to which session has maxIdleMs.
> _maxIdleMs=_manager._dftMaxIdleSecs>0?_manager._dftMaxIdleSecs*1000:-1;
>
> Where as the access method of JDBCSessionManager$Session is setting
> exprityTime on sessionData based on _maxIdleMs of Session which is zero. I
> think this is causing the issue.
>
>
>
>
> --
> View this message in context: http://jetty.4.n6.nabble.com/Jetty-clustering-not-working-properly-jettySessions-expiryTime-getting-set-to-0-after-sometime-tp4958537p4958540.html
> Sent from the Jetty User mailing list archive at Nabble.com.
> _______________________________________________
> jetty-users mailing list
> jetty-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jetty-users