hi,
another quick question that I haven't been able to find a suitable answer to
..
While the tomcat instance is restarting, getting its ducks in line and
generally sorting its life out, the apache end spits out a 503 (and 500)
error to the user on the outside end of the web connection.
While I have custom error pages configured at both the apache level (for
images and flat content) and the tomcat level (for not-found jsps), I don't
seem to be able to override the 503 error generated by mod_jk2.
Additionally, I have found that the "The servlet container is temporary
unavailable or being upgraded" clause is outside of the html of the error
page, which strikes me as odd.
Should I be able to override this 503, and should the normal Apache Error
handler definition ("ErrorDocument 503 /error503.html") be sufficient to
achieve this?
thanks,
Nick
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
