https://issues.apache.org/bugzilla/show_bug.cgi?id=51736
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
AssignedTo: [email protected]
ReportedBy: [email protected]
Classification: Unclassified
Default rpcTimeout that BackupManager sets to AbstractReplicatedMap is 15000
msec.
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
sessions.
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: 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: [email protected]
For additional commands, e-mail: [email protected]
