Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
MIME-Version: 1.0
In-Reply-To: <51cc7e06.4267320a.7961.ffffba4f@mx.google.com>
References: <51cc7e06.4267320a.7961.ffffba4f@mx.google.com>
Date: Tue, 2 Jul 2013 16:48:59 +0900
Message-ID: 
 <CAHHaTeGGjtV9bRqB+U=nBW_rm2AY7O5S3f2ZubsXgtSnpLPHww@mail.gmail.com>
Subject: Re: BackupManager start fails under heavy load
From: Keiichi Fujino <kfujino@apache.org>
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: multipart/alternative; boundary=089e0139ff4af431d604e0829371

--089e0139ff4af431d604e0829371
Content-Type: text/plain; charset=ISO-8859-1

2013/6/28 Patrick Savage <patrick.savage@3pillarglobal.com>

> 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?


No.
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.

-- 
Keiichi.Fujino

--089e0139ff4af431d604e0829371--