Thanks, Thomas, this is a useful information. Unfortunatelly, right now I'm
forced to use mod_jk 1.2.5 but we will switch to mod_jk2 in the near
future.

Regards,
Davor

Hubbert, Thomas wrote:

> Hi Davor,
> 
> if mod jk2 is an option I would suggest using that. It provides a couple
> of features that would help you achieving what you asked for. E.g. it
> supports graceful shutdown, i.e just redirecting already existing sessions
> with a valiud jvm route to one tomcat instance and sending all new
> requests to the other tomcat. Also in jk2 - if you don't care about
> loosing sessions - you can set one of the tomcats to be disabled making it
> unreachable for any requests. The good thing with jk2 is that it supports
> reloading of the conf file at runtime, i.e. without shuting anything down.
> 
> Hope this helps,
> Thomas
> 
> -----Ursprüngliche Nachricht-----
> Von: news [mailto:[EMAIL PROTECTED] Auftrag von Davor Cengija
> Gesendet: Freitag, 18. Juni 2004 09:47
> An: [EMAIL PROTECTED]
> Betreff: Pulling a node out of a cluster?
> 
> 
> My server configuration is as follows:
> 
> - Apache 2 + mod_jk 1.2.5
> - Two Tomcats 4.1.30 which communicate with mod_jk through ports 11009 and
> 12009.
> 
> It works just as it should; mod_jk automatically redirects all the
> requests from tomcat1 to tomcat2 when tomcat1 is down etc.
> 
> Now, the question is how to pull e.g. tomcat1 out of a cluster but to have
> it still happily running?
> 
> The best idea I could come to is to shut down a tomcat, change its mod_jk
> connector port and to bring it up again. Apache doesn't see that tomcat
> anymore and forwards all the requests to another one, and I can easily
> access that pulled-out tomcat through its http port. When I want to
> reconnect the pulled-out tomcat to cluster again I have to shut it down,
> change its mod_jk connector port back to its previous value and start it
> up again. It works but is a little bit touchy.
> 
> Any better idea?
> 
> I've seen a cluster configuration which uses special files, e.g.
> im_in_cluster.html which each clustered tomcat has in its web root. Load
> balancer first asks for that file and if it's available forwards request
> to that tomcat. Simply removing im_in_cluster.html file from a tomcat's
> webroot will render that tomcat unclustered. Any idea how could I achieve
> that with apache+mod_jk+two tomcats?
> 
> Thanks,
> Davor

-- 
Davor Cengija, [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to