-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

All,

On 10/31/2011 9:53 AM, Christopher Schultz wrote:
> I've only seen it once so far since switching-over to the NIO AJP 
> connector a few months back, but I figured I'd report it since I
> saw it.

I'm sure this was a fluke. After playing with the request that appears
to have caused this problem, I looked further back in my log files and
found a series of OOMEs which are almost certainly the source of the
problem.

Sorry for the noise.

- -chris

PS Is there anything to be done about connector state after an OOME?
Chuck contends that OOMEs aren't certain death for an application and
that recovery is possible.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk6urSgACgkQ9CaO5/Lv0PCn0QCeJJ8kNYI5HNLxQPWwSPc3poLP
KeQAnAupcjJ5b2tCAJyppLPYhkjVg1a2
=WIxB
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to