On Apr 17, 2009, at 8:28 AM, André Warnier wrote:
Rainer Jung wrote:
[...]
What remains for me is your suggestion, that the error is not a fatal
one, since there are other balanced workers left. We could include
such
a check in the startup code, although I'm not really convinced, that
your
Rainer Jung wrote:
[...]
What remains for me is your suggestion, that the error is not a fatal
one, since there are other balanced workers left. We could include such
a check in the startup code, although I'm not really convinced, that
your problem is a good reason for this.
I'm open to more
An interesting discussion. Since I am about to configure such a load
balancer and we prefer to use DNS, understanding this type of detail
is critical.
The OP said that the reason that the DNS did not resolve was that the
machine had been moved off the network. That may have been an event
?
;-)
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
--
View this message in context:
http://www.nabble.com/JK-1.2.28---load-balancer-worker-fails-on-startup-with-one
David Fisher wrote:
An interesting discussion. Since I am about to configure such a load
balancer and we prefer to use DNS, understanding this type of detail is
critical.
The OP said that the reason that the DNS did not resolve was that the
machine had been moved off the network. That may
On 17.04.2009 18:02, André Warnier wrote:
To my knowledge, the only case where the DNS would fail to provide an IP
address of a correctly-written FQDN name, is if you have some
configuration where your hosts register themselves under some variable
IP address when they startup. But that would
Rainer -
Wouldn't this type of dynamics occur if your workers were in a cloud?
Or if you needed a lot more very quickly for peak processing?
Am I correct to think that if someone is being so dynamic with their
worker's DNS configuration then they should automate using the status
worker
On 17.04.2009 21:44, David Fisher wrote:
Rainer -
Wouldn't this type of dynamics occur if your workers were in a cloud? Or
if you needed a lot more very quickly for peak processing?
Yes, but then you should extend your dynamics to your other
configurations as well. In fact there are
Scott Bradshaw wrote:
Yep - you are right on.
The machine was taken off the network and moved to a test network for a few
days. It currently does not resolve. If I change the host to its old IP
address (which does not respond), the system starts up just fine.
I would expect to see an error in
Still continuing to guess..
This is about efficiency.
If mod_jk had to do a DNS lookup each time it wants to send a packet to a
backend Tomcat (or at least each time it wants to create a new connection to
a backend Tomcat), that would be very inefficient.
So, instead, mod_jk stores the IP
On 16.04.2009 17:55, Scott Bradshaw wrote:
Still continuing to guess..
This is about efficiency.
If mod_jk had to do a DNS lookup each time it wants to send a packet to a
backend Tomcat (or at least each time it wants to create a new connection to
a backend Tomcat), that would be very
I apologize if this a silly question, but I can't figure it out! I've looked
over the documentation and I'm stumped.
I have 5 load balanced workers defined. I have them setup and configured
correctly.
workers.properties file (partial - not including all the individual workers)
balancer worker fails on startup with one
worker down ?
I apologize if this a silly question, but I can't figure it out! I've
looked over the documentation and I'm stumped.
I have 5 load balanced workers defined. I have them setup and configured
correctly.
workers.properties file (partial
?
-Original Message-
From: swbrads...@gmail.com [mailto:swbrads...@gmail.com] On Behalf Of
Scott Bradshaw
Sent: Wednesday, April 15, 2009 3:51 PM
To: users@tomcat.apache.org
Subject: JK 1.2.28 - load balancer worker fails on startup with one
worker down ?
I apologize if this a silly
: swbrads...@gmail.com [mailto:swbrads...@gmail.com] On Behalf Of
Scott Bradshaw
Sent: Wednesday, April 15, 2009 3:51 PM
To: users@tomcat.apache.org
Subject: JK 1.2.28 - load balancer worker fails on startup with one
worker down ?
I apologize if this a silly question, but I can't figure it out! I've
looked
@tomcat.apache.org
Subject: JK 1.2.28 - load balancer worker fails on startup with one
worker down ?
I apologize if this a silly question, but I can't figure it out! I've
looked over the documentation and I'm stumped.
I have 5 load balanced workers defined. I have them setup and configured
16 matches
Mail list logo
