tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 42849] - If mod_jk cannot resolve host name of single worker, all workers are destroyed
Date Sun, 15 Jul 2007 09:26:27 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=42849>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=42849


Tim.Whittington@orionhealth.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |




------- Additional Comments From Tim.Whittington@orionhealth.com  2007-07-15 02:26 -------
I think the point here is that startup isn't aborted (the log excerpt doesn't
show this).
What happens is that after the workers are shut down, Apache startup continues,
leaving mod_jk in an inconsistent state.
A request for a URI that should map to a worker then enters mod_jk, goes through
the URI -> Worker mapping process, and then fails to find the worker identified.

So what is happening is precisely the situation that we're trying to avoid -
starting Apache with a broken configuration.

This is with Apache 2.0.52 on CentOS 4, so it's a pretty standard setup.


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message