Christopher Schultz wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Filip,
Filip Hanik - Dev Lists wrote:
I'd recommend moving to mod_proxy_http, it will be easier for you to debug.
Bah! :(
that sounds knowledgeable :)
the error below seems to be more of a problem with apache (mod_proxy_ajp)
then with tomcat, tomcat is simply trying to write a message, but the
connection is no longer valid.
The problem is that the connection has been closed at some point. It's
usually because the user hit the STOP button on their browser and closed
the connection.
You can pretty much ignore these errors.
yes, and instead filling up the logs
No need to switch connectors.
actually, if you are gonna use AJP, use mod_jk, mod_proxy_ajp is not
moving in the same pace.
however, I'd recommend using HTTP, the HTTP connectors on tomcat are
finely tuned,
if there ever is a problem in the communication, you'll just put in a
sniffer and can see it direct.
but hey, don't listen to me :)
Filip
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGBA1E9CaO5/Lv0PARAqGMAJ90+P79Kt1Vhhm+a+aeNvdupzhJ4QCcDhzn
58umlhiChNndLXSputpG5rk=
=IxYN
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
