Hi, Can somebody go over the details of what exactly happens when tomcat instance has outOfmemory errors and there are following timeouts set in a loadbalancer worker config.
This is my understanding. ping_mode=A, ping_timeout=10000, reply_timeout=60000 and recorver_options=3 If the timeouts are set as above then CPing/Cpong test for connect and prepost will work. When a new real request is sent to this tomcat instance, it should hit reply_timeout because it has outofmemory errors. Then depending on no. of retries set (it is default, for me so 2), this instance will be tried once again. Second time also it should not get reply within reply_timeout and at that point it should be marked in "ERR" state. However, I don't see that. I don't see it being marked in "ERR" state. The state is still "OK" inspite of this tomcat instance having outofmemory errors. Could somebody explain what am I missing? Also, what does recorvery option mean in this case? Is it possible to explain what happens when I set recovery options? what happens when I set it to 3? What will happen if I set it to 7? I am really hoping to get more understanding of how this works. Thanks, Madhuri --- On Mon, 8/3/09, Madhuri Patwardhan <madhuri_patward...@yahoo.com> wrote: > From: Madhuri Patwardhan <madhuri_patward...@yahoo.com> > Subject: Re: after setting timeouts got puzzling results > To: "Tomcat Users List" <users@tomcat.apache.org>, a...@ice-sa.com > Date: Monday, August 3, 2009, 6:12 PM > > Hi, > > I am using apache 2.2.11 and mod_jk 1.2.28 and tomcat > version 5.5.27 and 5.5.20 > > Thanks, > Madhuri > > --- On Mon, 8/3/09, André Warnier <a...@ice-sa.com> > wrote: > > > From: André Warnier <a...@ice-sa.com> > > Subject: Re: after setting timeouts got puzzling > results > > To: "Tomcat Users List" <users@tomcat.apache.org> > > Date: Monday, August 3, 2009, 1:48 PM > > Madhuri Patwardhan wrote: > > > Hi, > > > > > > We are running with apache loadbalancer and 19 > tomcat > > workers loadbalanced. > > > I went through the timeout document and other > > documents, and my apache access log in detail before > > choosing the timeout values. I am seeing a bit > surprising > > results after setting timeouts. > > > > > > Earlier we did not have connect_timeout, > > prepost_timeout, reply_timeout, recovery_options and > > ping_mode set. After going through the documents and > > analyzing our application logs for timings I set the > > following values. > > > > > > ping_mode = A > > > reply_timeout=60000 > > > recorvery_options=3 > > > socket_connect_timeout=5000 > > > > > > Ping_timeout is set to the default value that is > > 10000. > > > > > > I saw that one of the tomcat instances had out > of > > memory errors and loadbalacer still showed that worker > in > > good state for 24 hours. I felt after setting these > timeouts > > infact it should have detected conditions like this > quickly. > > What am I missing? > > > > > One thing that is missing above, and would help > someone to > > answer, are the versions of Apache, mod_jk and Tomcat > you > > are using. > > (At least I suppose it is mod_jk). > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > > For additional commands, e-mail: users-h...@tomcat.apache.org > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
