DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5507>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5507

Swapping sessions causes exceptions and it doesn't work with FileStore

           Summary: Swapping sessions causes exceptions and it doesn't work
                    with FileStore
           Product: Tomcat 4
           Version: 4.0.1 Final
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: Catalina
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


If I use Manager configured for FileStore like
 <Context path="/dialogus" docBase="dialogus" debug="0"
                 reloadable="true">
          <Logger className="org.apache.catalina.logger.FileLogger"
                     prefix="dialogus." suffix=".log"
                  timestamp="true"/>
         <Manager className="org.apache.catalina.session.PersistentManager"
              debug="0"
              saveOnRestart="true"
              maxActiveSessions="1000"
              minIdleSwap="-1"
              maxIdleSwap="-1"
              maxIdleBackup="1800">
                <Store className="org.apache.catalina.session.FileStore"/>
          </Manager>
        </Context>

It causes many problems:
- There are two threads which expires sessions running concurently. First in store and 
second in 
persistent manager.
- The threads load each stored session, test if the one has to expire and (if yes) 
expire it. The 
problem of the mechanism is the harmless method StandardSession.setID(), which also 
stores 
the session to the manager. Why it is implemented so badly I don't know. The 
deserialization 
loads the session and uses the method setId() so during the tests for expiration the 
old stored 
session replaces the current, active session and all new values are lost and it is a 
big shame :-((((

I've posted the three patches to the tomcat-dev list. If it is incorrect, please 
rewrite the managing 
mechanism according these problems

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

Reply via email to