Honestly, I am very confused about this.
Here is my worker.properites
ps=\
worker.list=tomcat1, tomcat2, loadbalancer
#------tomcat1 configuration----
.....
#------tomcat2 configuration----
.....
#-------Load balancer worker --
worker.loadbalancer.type=lb
worker.loadbalancer.balanced_workers= tomcat1, tomcat2
I have two tomcat instances tomcat1 and tomcat2 running on different
box(WinNT).
What I want is in mod_jk.log, when the message is related to tomcat1, it
will shows tomcat1;
And same to tomcat2. This way I can be clear which tomcat has problem, if
there is, without logon to the physical machine where the tomcat instance
runs.
The current problem is with my mod_jk.conf is
JkMount /* loadbalancer
It always shows loadbalancer in mod_jk.log
If my mod_jk.conf is like
JkMount /* tomcat1
JkMount /* tomcat2
Only tomcat2 being processed by apache. It doesn't work the way I want.
Help !!!
-Simon
-----Original Message-----
From: Antonio Fiol Bonnín [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 19, 2004 2:22 PM
To: Tomcat Users List
Subject: Re: How to detect tomcat down
Hi,
You are looking for "lb" type workers (even if you did not know). Look
for that in Tomcat docs.
In short:
JkMount /* balancer
worker.balancer.type=lb
worker.balancer.workerlist=tomcat1worker,tomcat2worker
(I am not sure about the "workerlist" word. It might be "workers" or
"list"... Search for an example in your sample workers.properties)
Antonio Fiol
Simon Zeng wrote:
>It seems working !!! However, I have a problem with the configuration.
>
>All my tomcat workers share the same code base and is ready to handle all
>the requests in load balance mode. I want something like this:
> JkMount /* tomcat1worker
> JkMount /* tomcat2worker
>
>However, it only pick up tomcat2worker. For example, if I have tomcat2 down
>and tomcat1 up. The mod_jk.log always give me error for tomcat2 without
>going to tomcat1.
>
>Is there any way to solve this? Many thanks.
>-Simon
>
>-----Original Message-----
>From: Tim Funk [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, May 19, 2004 10:43 AM
>To: Tomcat Users List
>Subject: Re: How to detect tomcat down
>
>
>(Syntax below is not exactly correct, but has the right idea)
>
>Assuming you loadlancer worker is named loadbalanceworker which has workers
>tomcat1worker and tomcat2worker
>
>Instead of
>JkMount *.jsp loadbalanceworker
>
>Try this
>JkMount /testworker1page tomcat1worker
>JkMount /testworker2page tomcat2worker
>
>
>-Tim
>
>Simon Zeng wrote:
>
>
>
>>Could you please explain what do you mean special (hidden) and how to do
>>
>>
>it?
>
>
>>Currently I only define on JkMount for loadbalancer. Thanks, -Simon
>>
>>-----Original Message-----
>>From: Tim Funk [mailto:[EMAIL PROTECTED]
>>Sent: Tuesday, May 18, 2004 7:54 PM
>>To: Tomcat Users List
>>Subject: Re: How to detect tomcat down
>>
>>
>>For the load balanced tests, have a special (hidden) JkMount for each
>>
>>
>tomcat
>
>
>>in the cluster.
>>
>>
>>-Tim
>>
>>Simon Zeng wrote:
>>
>>
>>
>>>I can come up with a WatchDog to do the monitoring/restart. But We have a
>>>few tomcat instance runing in load balance mode with one Apache
>>>
>>>
>>dispatching
>>
>>
>>
>>>request to them. How could we figure out if one/more(not all) tomcat
>>>instances down and how to decide which ones they are? Basically the
>>>
>>>
>>question
>>
>>
>>
>>>is can we bypass Apache to go directly to Tomcat since we know where they
>>>are?
>>>
>>>Thanks,
>>>-Simon
>>>
>>>-----Original Message-----
>>>From: QM [mailto:[EMAIL PROTECTED]
>>>Sent: Tuesday, May 18, 2004 4:40 PM
>>>To: Tomcat Users List
>>>Subject: Re: How to detect tomcat down
>>>
>>>
>>>On Tue, May 18, 2004 at 03:04:28PM -0400, Simon Zeng wrote:
>>>: I am running Apache 2.0.47 and Tomcat 4.1.24 on Win2K/NT. I would like
>>>
>>>
>>to
>>
>>
>>
>>>: monitor the tomcat
>>>: server and restart it automatically if it is detected down. I did a lot
>>>: research but could not find any convincing way to do it.
>>>
>>>Some commercial monitoring products perform a request to an
>>>(unprotected) URI and, in the event of a failure, perform some specified
>>>action. -that is, call the start script.
>>>
>>>Otherwise, you could have Tomcat started by a (custom) watchdog, the
>>>idea being that it kicks the start script if the expected process isn't
>>>running. I recall iPlanet 4 did something similar.
>>>
>>>As for free + out-of-the-box solutions, I haven't seen any...
>>>
>>>-QM
>>>
>>>
>>>
>>---------------------------------------------------------------------
>>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]
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
