Hi,
when you set a load balancer (mod_jk v1.2.26) with 2 workers:
worker.myWorker.type=lb
worker.myWorker.balance_workers=tc1Worker, tc2Worker
and one of the worker's host cannot be resolved:
worker.tc2Worker.host=mytest.mydom.com
Then Apache will not start.
- since the other worker is 'good', should'nt we let apache start with a
nice error message informing you that one worker could not resolved (done
today) and jk will disable the worker and let apache start anyway?
- Adding a disable does not fix the issue it seems. Only removing the
worker from the list does.
worker.tc2Worker.activation=d
The idea is that if DNS fails to resolve a host (some admin mistake) and
Apache was restarted automatically for unrelated reasons, it would fail to
come back online without a manual intervention - editing a configuration
file (which might be a challenge).
Rgds - Fred
--
View this message in context:
http://www.nabble.com/Apache-fails-to-start-when-.host-does-not-resolve.-tp16422828p16422828.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To start a new topic, e-mail: [email protected]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
