Bernd's earlier message about maxconnections led me to the code that
explains your "connection closed" problem.
maxconnections limits the number of connections that AOLserver can be
servicing simultaneously. The server pre-allocates enough space for
that many simultaneous connections, which defaults to 100 in
AOLserver 3.5.6. If you are servicing 100 connections, AOLserver's
Ns_QueueConn function will begin to return NS_ERROR when called upon
to append a connection to the run queue.
nsopenssl 2.x manages its own connection services separately from
AOLserver, and I have nsopenssl closing the connection when
Ns_QueueConn returns with something other than NS_OK. The AOLserver
3.5.6 processing code holds the connection until it can process it,
which is the right thing to do.
So nsopenssl is at fault here, and that is my fault, and you have my
apologies.
This problem can be fixed. Those of you still using nsopenssl 2.x for
PRODUCTION services that have experienced this problem or may in the
future, please contact me directly at [EMAIL PROTECTED] I do not want
to do work on this legacy code unless people are using this in their
business and may be losing clients or money as a result.
By the way, nsopenssl 3.x used with AOLserver 4.x shouldn't have
this problem because the connection servicing code is all in
AOLserver, with a callback to nsopenssl for the SSL portion.
Thanks for your patience.
/s.
On Jul 22, 2006, at 8:59 PM, Scott Goodwin wrote:
AOLserver actually manages the connections for nsopenssl. The
nsopenssl code in question is:
if (Ns_QueueConn(sdPtr->driver, scPtr) != NS_OK) {
Ns_Log(Warning, "%s: connection dropped", sdPtr->module);
(void) SockClose(scPtr);
}
nsopenssl is getting something other than NS_OK back from
Ns_QueueConn when the latter tries to append the connection to the
run queue. AOLserver in turn may not have been keeping up with the
load, but I'd first check your OS TCP pending connection limits. If
your system was being hammered, it's possible your OS was turning
away conns. I'm not sure I should have put this message in the log
as it may not reflect what actually happened. Unless someone
responds with a better answer, I'll take a closer look at the code
tomorrow.
/s.
On Jul 22, 2006, at 7:45 PM, William Scott Jordan wrote:
Hi all!
We had a situation recently of extremely high traffic, during
which connections were being rejected/dropped with following
warning showing up in the logs: "Warning: nsopenssl: connection
dropped" I guess my questions are, what "limit" in nsopenssl is
causing connections to be dropped? Can this limit be adjusted?
Is there any way to catch this error to allow for a more graceful
degredation, such as with a redirect to an unencrypted "Server Too
Busy" page?
This is on AOLServer 3.5.6, nsopenssl 2.1a, and FC3.
Any light that anyone can shed on this would be greatly appreciated.
-Scott
--
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.
--
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.
--
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.
