Scott Eade <[EMAIL PROTECTED]> writes:

>Henning P. Schmiedehausen wrote:

>>Michal Frackowiak <[EMAIL PROTECTED]> writes:
>>  
>>
>>>I have a diffrent entry in Tomcat's logs. just after a tomcat is 
>>>started, my app throws an error. what helps is reloading app using the 
>>>manager application. but when I start tomcat and try to use my app I get 
>>>an entry in logs:
>>>    
>>>
>>
>>Do you really need session persistence over container restarts? If not,
>>configure your container to not save the sessions.
>>  
>>
>While I haven't checked the latest tomcat release, certainly up to now
>the mechanism provided to stop the sessions from being persisted across
>a context reload/container restart does not in fact work.

>I have made the script I use to start tomcat delete the persisted session
>file.  If it is a system that I alone am testing the problem usually does
>not occur if I logout before I reload the context manually - if you auto
>reload then you are probably going to have to restart manually in order
>to clear the persisted sessions (as suggested by Michal).

Huh? Which manager are you using for Tomcat? If you use the
org.apache.catalina.session.StandardManager there shouldn't be a
problem except for the restart persistence which you can work around
by setting pathname="" in the manager definition of Tomcat (at least
4.1 you can do this).  (Though I end up removing the SESSIONS.ser file
from the temp dir too. ;-) )

You might even get away with

--- cut --- 
package de.intermeta.catalina;

import org.apache.catalina.session.StandardManager;

public class NonloadingManager
        extends StandardManager
{
        public void load()
        {
                recycled.clear();
                sessions.clear();
                if(debug >= 1)
                        log("Skipping reload of persistent sessions");
        }
}
--- cut --- 

and use this one in your server.xml ;-) 

If you're using org.apache.catalina.session.PersistentManager with a
store, well this bugger isn't marked "WARNING - Use of this Manager
implementation has not been thoroughly tested, and should be
considered experimental!"  without any good reason. :-)

        Regards
                Henning


>It would be great to eventually track down the culprit.

>Scott

>-- 
>Scott Eade
>Backstage Technologies Pty. Ltd.
>http://www.backstagetech.com.au





>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]

-- 
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen          INTERMETA GmbH
[EMAIL PROTECTED]        +49 9131 50 654 0   http://www.intermeta.de/

Java, perl, Solaris, Linux, xSP Consulting, Web Services 
freelance consultant -- Jakarta Turbine Development  -- hero for hire

"Dominate!! Dominate!! Eat your young and aggregate! I have grotty silicon!" 
      -- AOL CD when played backwards  (User Friendly - 200-10-15)

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to