(Something's wrong with the embargo system on Nabble.)
Running Jetty 6.1.14 on linux, java 1.6.0_07, with a custom streaming handler (extends AbstractHandler).
When some clients disconnect, usually clients that sent parameters in the body of their request, they leave behind a socket in CLOSED_WAIT with one byte of input. The handler is still active and continues to stream to the client.
Before the client closes, netstat shows 0 bytes of waiting input and typically 0 bytes of waiting output. After the client closes, the connection shows 1 byte of input, and an arbitrary amount of output waiting.
Where is this input coming from? Is it truly data, or is it some form of out of band sentinel in the TCP stream?
What can I do to get the handler to close completely?
-John Kalucki
