At Tuesday 02:58 PM 10/26/2004, Steve wrote:
I will apply it and remake the module to see if it helps. Thanks. Off
hand can you remember what symptoms you saw with your 2.1a problems? Did
the server restart? Did you get browser errors? Did it log errors? I'm
just trying to see if your problem correlates with mine.
It logged errors like the following...:
[02/Jun/2003:08:51:09][2634.98316][-conn4-] Error: nsopenssl: sockclient:
connection closed by peer
...which comes from the one function that represents the only substantive
change between nsopenssl 2.1 and 2.1a: NsOpenSSLRecv().
I never did get the full details of the failures, but this was a
description I received from the development staff: "Servers posting to
themselves report a connection failure. In other places in the
application, we just get weird and intermittent failures."
We'd deployed 2.1a during a QA cycle, and it caused so many problems in QA
that we just immediately pulled it and went back to 2.1. After we
reverted to 2.1 the failures disappeared.
- John
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of
your email blank.
