tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Keiichi Fujino <>
Subject Re: BackupManager start fails under heavy load
Date Tue, 02 Jul 2013 07:48:59 GMT
2013/6/28 Patrick Savage <>

> We have an issue in our Tomcat 7.0.30 clustered production environment on
> RHEL 5 where Tomcat fails to start our application when other nodes in the
> cluster are under extremely heavy load. It fails because the BackupManager
> cannot start the replicated map due to timeouts trying to connect to all
> the
> other nodes. The only way to recover from this seems to be shutting down
> almost all of the nodes and then starting them again. The cluster has 9
> nodes, but we have also had the problem with 6 nodes.
> Is there a way to ensure the application will start even if the
> BackupManager cannot connect to the other nodes?

If replication map fails to start, associated context will fail to start.

I will implement a feature  to ensure the application will start even If
replication map fails to start.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message