Actually TIME_WAIT is normal - when you close a connection, it goes to timewait for a set amount of time and then is closed, this stops any delayed packets being accepted by a later connection. There are kernel/tcp params to determine how long it should be in timewait. If you have too many at timewait this is called TIME_WAIT loading and can have implications on server performance as each of these has a memory stack.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Kevin King Sent: 02 September 2009 19:07 To: U2 Users List Subject: [U2] callHTTP - disconnect? I have a Unidata (6.1/AIX) program using the callHTTP API to move data out to an Apache server on a transaction by transaction basis. When the transactions get dropped into the queue slowly all is well. When the transactions get flooded in, Apache gets overwhelmed. It appears like Unidata isn't sending a disconnect after the submitRequest because the TIME_WAIT in netstat is showing excessively long disconnect times for these connections. I don't see anything in the API documentation that mentions disconnecting from the Unidata side; is there a header or option that I can set to make sure Unidata sends a disconnect after the request? -Kevin http://www.PrecisOnline.com _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
