We might have just fixed each other's problem.

I have the exact opposite problem (with Tomcat5) - I need to drop the sessions when I redeploy, since new versions might carry different objects and one of my objects is not serializable yet. And I don't need to preserve the sessions across vanilla server restarts either.

Even when I did nothing to define persistence (no Manager clause at all) Tomcat would not drop the sessions even when I stopped, redeployed or went to the Manager HTTP console and stopped it there.

So, try removing the <Manager> clause altogether.

I'll try adding yours to my setup and see if it successfully kills my sessions.

-----Original Message-----
From: ext Steven Job [mailto:tomcat@(protected)]
Sent: Wednesday, January 14, 2004 3:59 PM
To: tomcat-user@(protected)
Subject: Session Persistance


Ok, I don't know what is wrong. I thought I had this working before.

Yet when I stop and restart Tomcat I loose my session. Even though I see
the file being saved.


      <Context path="" docBase="ROOT" debug="0">
     <Manager className="org.apache.catalina.session.PersistentManager"
        debug="0"
        saveOnRestart="true"
        maxActiveSessions="-1"
        minIdleSwap="-1"
        maxIdleSwap="-1"
        maxIdleBackup="-1">
          <Store className="org.apache.catalina.session.FileStore"
directory="/root/sessions" />
      </Manager>
      </Context>


Can someone shed some light on this and let me know what is wrong with my
configuration?


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)