Well, it definitely looks like something to look into. Thank you.
I was thinking about HA options and found this one to be so easy, that wonder why people are not using it. Now, you say, >I have users that may work on a session for several hours sometimes Is this a think-time issue (are they editing a text or something?) or long-running back end queries? I don't know exactly 'where the shoe hurts', but in the first case I would just give them a JNL-based application to play with and for the second case I would use run JDBC queries from JMS and somehow keep a tag on the query. I hope this gave you some ideas ----- Original Message ----- From: "Richard Mixon (qwest)" <[EMAIL PROTECTED]> To: "Tomcat Users List" <tomcat-user@jakarta.apache.org> Sent: Thursday, January 27, 2005 10:15 AM Subject: RE: loadbalancing with mod_jk 1.2.8 > John, > > From what I gather, this is the purpose of the properties "local_worker" > and "local_worker_only" properties in the workers.properties file. They > are documented at the bottom of this page: > http://jakarta.apache.org/tomcat/connectors-doc/config/workers.html > > Unfortunately the explanation is not clear - partially due to the > English. I say this somewhat apologetically - realizing of course that > the writers command of English if probably far, far better than my > command of their native language. > > From what I do understand: > 1) At the point that you decide to do maintenance on one machine, you > need to change your workers.properties and set local_worker=0 for that > particular machine. > 2) Then do a "reload" on your Apache configuration. > 3) JK will then stop directing new traffic to the designated machine. > 4) After all sessions have expired or quiesced you can stop that Tomcat > instance and do the maintenance. > > The above scenario may work for some, but not for my case. I have users > that may work on a session for several hours sometimes. So I need to use > JK and Tomcat session replication which is supposed to let you use the > "ant stop" command and have all traffic immediately handled by the other > Tomcat instances. There is a separate active thread on this issue. I see > Filip just mentioned a new valve "JvmRouteBinderValve" that may help > solve my problem. > > Hope this helps - Richard > > -----Original Message----- > From: John Smith [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 27, 2005 2:12 AM > To: Tomcat Users List > Subject: Re: loadbalancing with mod_jk 1.2.8 > > > I do know how to stop TC, I said the whole idea for people to know I > was > thinking about an HA set up using Apache + TC instances > > The part I am most interested in is,namely; how to make the connector > at > run time NOT send NEW connections to one the tomcat instances being used > for > loadbalancing > > ----- Original Message ----- > From: "Graham Bleach" <[EMAIL PROTECTED]> > To: "Tomcat Users List" <tomcat-user@jakarta.apache.org> > Sent: Wednesday, January 26, 2005 6:04 PM > Subject: Re: loadbalancing with mod_jk 1.2.8 > > > > On Wed, Jan 26, 2005 at 01:41:25PM -0500, John Smith wrote: > > > Is there any way to make the connector at run time to NOT send NEW > > > connections to one the tomcat instances being used for > loadbalancing, > and > > > then reload this TC instances once all sessions to it have timed > out? > > > > If you stop the tomcat instance with the command > > $CATALINA_HOME/bin/catalina.sh stop > > > > I believe tomcat waits for threads to finish what they are doing > > before it actually terminates. > > > > > > G > > -- > > Privacy is a transient notion. It started when people stopped > believing > > that God could see everything and stopped when governments realised > there > > was a vacancy to be filled. > > -- Roger Needham > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
