This problem occure when we have the load blance to to see if the C:D is
up by probing the port , this is corrected. Now it seems we have user
write API to to talk to C:D and it causing the problem.
Do you guys feels reducing the default 180000 for the TCP-TIME-WAIT
BUCKETS POOL SIZE will correct the problem?
Also if this is the case, does this means that a users can bring down the
server by not closing the socket correctly(DoS) ???
. currently, we have to re-boot box.
David Boyes
<[EMAIL PROTECTED]
e.net> To
Sent by: Linux on
390 Port LINUX-390@VM.MARIST.EDU
<[EMAIL PROTECTED] cc
IST.EDU>
11/15/2006 05:10
PM
Subject
Re: "Close-wait"
Please respond to
Linux on 390 Port
<[EMAIL PROTECTED]
IST.EDU>
> I think the close-wait is a coincidence. You need to find out if
there
> are any processes that are actually stuck on something.
I'd concur. Close-wait is often caused by the process on the other end
of the connection terminating without shutting down the connection
properly. If something is causing this, that's the root of your problem.
If something in Connect:Direct is waiting for the connection to close to
do something else (like trigger an arrival event, etc), that's a
different problem, and is probably what's causing the thread in C:D to
ignore the signal.
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
-----------------------------------------
This message and its attachments may contain privileged and
confidential information. If you are not the intended recipient(s),
you are prohibited from printing, forwarding, saving or copying this
email. If you have received this e-mail in error, please immediately
notify the sender and delete this e-mail and its attachments from your
computer.
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
