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 45317] New: DeltaManager always reports default timeout value for receiving session state on startup
Date Tue, 01 Jul 2008 14:50:36 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=45317

           Summary: DeltaManager always reports default timeout value for
                    receiving session state on startup
           Product: Tomcat 6
           Version: 6.0.16
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: trivial
          Priority: P5
         Component: Cluster
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: viktor.radnai@gmail.com


Hi there,

If I override the state transfer timeout:
          <Manager className="org.apache.catalina.ha.session.DeltaManager"
                   stateTransferTimeout="10"
                   expireSessionsOnShutdown="false"
                   notifyListenersOnReplication="true"/>

DeltaManager continues to log the default timeout value (ie: "This operation
will timeout if no session state has been received within 60 seconds."):

2008-07-01 14:31:30,419 WARN [org.apache.catalina.ha.session.DeltaManager] -
Manager [localhost#/manager], requesting session state from
org.apache.catalina.tribes.membership.MemberImpl[tcp://{10, -64, 104,
-55}:15000,{10, -64, 104, -55},15000, alive=18586,id={-62 91 -70 -63 -111 50 70
-33 -104 41 -48 -32 91 34 -83 -55 }, payload={}, command={}, domain={}, ]. This
operation will timeout if no session state has been received within 60 seconds. 
2008-07-01 14:31:35,310 WARN [org.apache.catalina.ha.ClusterListener] - Context
manager doesn't exist:localhost#/host-manager 

But it actually uses the correct timeout value (ie: "timing out after 10,100
ms"):

2008-07-01 14:31:40,518 ERROR [org.apache.catalina.ha.session.DeltaManager] -
Manager [localhost#/manager]: No session state send at 01/07/08 14:31 received,
timing out after 10,100 ms. 

This is only an incorrect message, but it is quite annoying especially coupled
with the fact that the above configuration is only documented for tomcat 5
(where syntax is subtly different).


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

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


Mime
View raw message