You configured 404 as an http status code, which results in taking
workers offline. I think usually this is not a good idea. Think about
users sending you URLs like
http://youserver/trash
and thus taking your backends offline :(
Even without bad things in mind, users might use old bookmarks after you
upgraded your app and whops again your backend gets offlined.
404s are not nice but unfortunately they seem to be part of most webapps
the software industry produces.
Regards,
Rainer
ben short wrote:
Hi All,
I set the jk logging level to debug and noticed that the jsp page was
trying to get an image from from tomcat that didnt exist. This lead
the jk mod to set both tomcat workers to an error state. Im guessing
that the next request I tried got sent to a tomcat and then a new
session was created.
I have fixed the link and now it all works ok.
...
worker.jcpres1.fail_on_status=404,503
...
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
