tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 29035] New: - wrong sessionId in EVT_SESSION_ACCESSED message
Date Mon, 17 May 2004 14:13:32 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=29035>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29035

wrong sessionId in EVT_SESSION_ACCESSED message

           Summary: wrong sessionId in EVT_SESSION_ACCESSED message
           Product: Tomcat 5
           Version: 5.0.24
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Catalina:Cluster
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: rainer.jung@kippdata.de
                CC: rainer.jung@kippdata.de


Hi,

in the cluster module in class session/DeltaManager there is a small buglet in
line 799. When sending EVT_SESSION_ACCESSED from a primary node the message is
created using the sessionId plus timestamp as a sessionId. This session will not
be found on the receiving side. Just seperate sessionId from uniqueId in the
message creation like in line 788. The patch is:

atlas1% diff session/DeltaManager.java session/DeltaManager.java_patch
798a799
>                                              sessionId,

The line numbers are the same in CVS HEAD and in 5.0.24. The patch applies to both.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message