You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2003/07/08 16:32:04 UTC
DO NOT REPLY [Bug 21290] -
Progressive failure of MAC Message Decoding in HTTPS handler (lib(20):ssl func(143):reason(1109))
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21290>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21290
Progressive failure of MAC Message Decoding in HTTPS handler (lib(20):ssl func(143):reason(1109))
ksnider@flarn.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Sudden total failure of MAC |Progressive failure of MAC
|Message Decoding in HTTPS |Message Decoding in HTTPS
|handler (ssl |handler (lib(20):ssl
|func(143):reason(1109)) |func(143):reason(1109))
------- Additional Comments From ksnider@flarn.com 2003-07-08 14:32 -------
Further information:
On investigation, it does appear that this problem is *not* sudden - restarting
apache leads to the problem re-occuring after a period of hours, then becomes
progressively worse.
It's as if each worker thread is somehow ending up in an "inconsistent" state,
and from that point on, failing on connects. As we have 200 threads running on
these high-volume servers, it takes some time for enough threads to be adversely
affected to actually trip our monitoring system.
Also, since these errors *do* occur sporadically, but I can't seem to catch the
error itself until it reaches "critical mass", there's also a possiblity that
apache is somehow masking the problem until it exceeds its' ability to do so,
perhaps?
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org