Hi Chris,
client errors in jk log are always errors occurring when mod_jk tries to
write back what it got from the backend using web server APIs to the
client of the web server (user, browser etc.). So they point to a
problem between and including the web server and something in front of it.
Especially during performance problems, client errors are expected as a
consequence, because whenever people try to reload, the browser closes
the original connection and sending back response data via this
connection later fails.
Best regards,
Rainer
Am 23.03.2022 um 13:08 schrieb Christopher Schultz:
All,
What kinds of things will cause a "client error" in mod_jk's accounting?
Does that mean things like unexpected disconnects on the part of the
remote client (i.e. web browser), or does it mean failure of the jk
module itself to connect (as a client) to the back-end Tomcat?
I'm starting to see situations where we have small numbers of client
errors occurring "all the time", meaning that we accumulate maybe 10-20
per day. If that's web browser disconnects then I don't care at all. If
it's a problem I have with my internal networking and
resource-allocation, then it's something I have to adjust.
Thanks,
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
