tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 51736] New: Make rpcTimeout configurable in BackupManager.
Date Mon, 29 Aug 2011 10:26:09 GMT

             Bug #: 51736
           Summary: Make rpcTimeout configurable in BackupManager.
           Product: Tomcat 7
           Version: trunk
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Cluster
    Classification: Unclassified

Default rpcTimeout that BackupManager sets to AbstractReplicatedMap is 15000
This is not configurable.

When receiving MapMessage.MSG_START (and after a new member is added), 
publishEntryInfo is called for all sessions where primary and backup node are
not included. 
And, the backup node is set to the session.

When only one Tomcat starts in cluster, publishEntryInfo will be called for all
As a result, the RPC message has the possibility of the timeout. 

When acquiring session from restarting Tomcat, 
warning of "Unable to retrieve remote object for key:XXX" is logged.
And the session cannot be continued. 

I make rpcTimeout configurable in BackupManager.
Additionally, if RPC message timeouted in AbstractReplicatedMap#broadcast, add
warning message.

Best Regards.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message