Loading ...
Sorry, an error occurred while loading the content.

311TIME_WAIT for daemon

Expand Messages
  • Craig Kelley
    May 13, 2001
      I've noticed that while using the HTTP::Daemon version of SOAP::LITE the
      sockets go into TIME_WAIT for quite some time before expring. I've had
      this problem with some C socket code in which there was still information
      in the buffer to be delivered after the other end closed the connection.
      Is there some call I need to make to flush a connection, or should I just
      move it over to apache (I really like the persistent state and simplicity
      of the built-in daemon though).

      -Craig

      PS: Here's a listing from netstat:

      tcp 0 0 localhost.localdom:1983 localhost.localdo:37454 TIME_WAIT
      tcp 0 0 localhost.localdom:1983 localhost.localdo:37453 TIME_WAIT
      tcp 0 0 localhost.localdom:1983 localhost.localdo:37452 TIME_WAIT
      tcp 0 0 localhost.localdom:1983 localhost.localdo:37451 TIME_WAIT
      tcp 0 0 localhost.localdom:1983 localhost.localdo:37450 TIME_WAIT
      tcp 0 0 localhost.localdom:1983 localhost.localdo:37460 TIME_WAIT
      tcp 0 0 localhost.localdom:1983 localhost.localdo:37459 TIME_WAIT
      tcp 0 0 localhost.localdom:1983 localhost.localdo:37465 TIME_WAIT

      (and this is from a relativly simple transaction)
    • Show all 2 messages in this topic