On 18/02/2010 23:42, Leon Kolchinsky wrote:
Constrains of the application :(
You can't run 2 instances in same time on the same DB.
That's why I have to configure "Cold Failover" for that I need to find
out that Tomcat is in unresponsive state to shut it down completely and
start it on another server.
In that case, maybe start the alternate server, but not the application.
If the original is unresponsive then shutting it down without local
access to that machine could be quite hard.
But what's the best way (or may be the only way) to achieve that?
Unless anyone else on the list knows something about mod_jk capabilities
with regard to starting / stopping a server, I think you've looking at:
server1.app1 : monitored by server2.app1
server2.app1 : monitoring app
server2.app2 : duplicate app
Where server2.app2 is not started, but can be started by server2.app1,
perhaps using the manager app JMX API.
In any case you're looking at a 3rd application to perform the
monitoring & management. Admin notification could occur on any app startup.
p
On Fri, Feb 19, 2010 at 10:11, Pid <p...@pidster.com
<mailto:p...@pidster.com>> wrote:
On 18/02/2010 22:49, Leon Kolchinsky wrote:
Anyone guys?
Any insights on the following?
Thanks
On Thu, Feb 18, 2010 at 13:48, Leon
Kolchinsky<lkolc...@gmail.com <mailto:lkolc...@gmail.com>> wrote:
Hello All,
My current interest is to install "Confluence" -
http://www.atlassian.com/software/confluence/
in a "Cold Failover" mode.
I'm currently running ApacheHttpd in front of Tomcat6 using
mod_jk module
and I prefer to leave Apache Httpd in front of Tomcat.
This is java application is using DB (Oracle in my case) and
some kind of
local caching technique (to make things run faster I presume).
So there must be only one "Confluence" application at a time.
I would like to configure"Cold Failover" in such a way that
the moment
current Tomcat instance become unresponsive, the command
will run killing
tomcat+"apache httpd" and starting another
tomcat+"apache httpd" on another server (or just killing
tomcat, but I'm
not sure that it's doable, since it's not a regular
loadbalancer worker
setup).
I'm not sure that's doable either. If you've got a spare server,
why not just have the other instance already running?
p
I know that there is a possibility to use 'Advanced worker
directives' like
connect_timeout, prepost_timeout and reply_timeout but I'm
not sure that
it's implementable in my case.
Any suggestion on proposed configuration?
May be there are some other ways to achieve what I want?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
<mailto:users-unsubscr...@tomcat.apache.org>
For additional commands, e-mail: users-h...@tomcat.apache.org
<mailto:users-h...@tomcat.apache.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
