>> To clarify - this is not a replacement or an 'exclusive' mechanism. >> The 'ajp14' based config, where tomcat sends notifications to apache >> remains. > >Seems like I was reinventing the wheel there for a while. So >AJP14 knows >how configure itself from the running Tomcat... Pretty cool in my book!
That was one of the important evolution of ajp14 in regard of ajp13. >> The problems with 'tomcat sending config info to apache' ( and why I >> would not make that the 'default' simple config ): >> >> 1. It requires a strict startup sequence ( tomcat before apache ). >> Otherwise, if tomcat is not started apache will respond '404' for >> what it doesn't recognize, instead of 'temporary >unavailable' or 'context >> is down'. This can be very problematic for users ( who'll >assume the url >> is wrong instead of try again later ). > >This is easily achieved (that's how I run my boxes) through the startup >script when both Apache and Tomcat are on the same box. I call this >thing 'was' -> Web Application Server. Here is the sample (RH Linux >7.0): Pretty the same stuff in my RPM for TC 3.3 :) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
