2 Replies Latest reply on Apr 7, 2006 11:37 AM by dannie

    session persistance

    dannie

      Hi,
      until some days ago I was using jboss 4.0.1; now I've installed jboss 4.0.3. With the 4.0.1 version, if I have an active session and I re-deploy the application (while the server is up), the session persists; now, with the 4.0.3. version, I have to login every time. I've searched some informations in the documentation and I found (http://tomcat.apache.org/tomcat-5.5-doc/config/manager.html):

      Whenver Catalina is shut down normally and restarted, or when an application reload is triggered, the standard Manager implementation will attempt to serialize all currently active sessions to a disk file located via the pathname attribute. All such saved sessions will then be deserialized and activated (assuming they have not expired in the mean time) when the application reload is completed.

      So, I'm wrong with some basic configurations?

        • 1. Re: session persistance
          dannie

          It doesn't create SESSIONS.ser file... well, more in detail, it creates it for an application that has its specific Context element in the server.xml file, but doesn't create it for applications that are in the deploy folder and haven't explicit <Context ....> description...

          • 2. Eureka!
            dannie

            Solution found! It's necessary to uncomment the Manager element in context.xml (file that non exists in jboss 4.0.1):

            <Manager pathname="SESSIONS.ser" />