Forum OpenACS Improvement Proposals (TIPs): Re: TIP #51 - require AOLserver 4.x for OpenACS 5.2

Collapse
Posted by Cathy Sarisky on
For folks not following the AOLserver mailing list, here's something from Jamie Rasmussen:

We see nsopenssl eating the CPU too - the cause seems to be an infinite
loop in NsOpenSSLConnHandshake.  You can see it if you use Netscape/Mozilla
and your domain name doesn't match the certificate.  It also seems to
happen when the domain name matches but you close the browser window during
the handshake. (I haven't had the chance to confirm what error that
triggers.)

Scott has been looking into this, and thought that a solution could require
changes to the core because of the aggressive read-ahead in AOLserver 4.x.
As a temporary measure, he is also considering adding a timer to the conn
that would exit the loop if no data has been read over the specified period.

---
Several folks hosting with me have seen issues...