> 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
