Channels being possibly reused in with-channel, causing exceptions with threads about http-kit HOT 4 CLOSED

http-kit reuses the AsyncChannel object. AsyncChannel is per connection. A connection is a TCP connection. Since browser or JMeter will try to use the TCP connection, AsyncChannel get reused. When reused, AsyncChannel get reseted https://github.com/http-kit/http-kit/blob/master/src/java/org/httpkit/server/AsyncChannel.java#L73

Since the reset is lazyset, maybe this is where the problem is.

http-kit only allow set the closeHandler once, maybe this is a bad design. How do you think about it?

As regarding the multiple threads, how about this:
Do not use PipedInputStream or PipedOutputStream. Instead of write to the PipedOutputStream, just write to channel. http-kit is multi-threaded, blocking a few thread will be fine. Set :thread option to a larger value will be fine http://http-kit.org/server.html#options

from http-kit.

This helped so much! Thank you, @shenfeng.

As for only allowing the closeHandler once, I think it's ok, although it is confusing since the reset is lazyset and you can encounter a situation where you think the closeHandler is not set but it actually is.

When you say "just write to channel," what do you mean, exactly? I am generating a stream of JSON or XML text and need an OutputStream for it to go into. The channel's not an OutputStream, so I'm not certain the best way to go about that.

from http-kit.

I will try to reproduce and fix the issue with closeHandler, It maybe a multi thread bug of http-kit.

The channel's not an OutputStream

You can create a method, like:
ch->outputstream

(defn ch->outputstream [ch]
  (proxy [java.io.OutputStream] []
    (close []
       )
    (write
      ([bs] ;; bytes of byte
             ;; write to channel
         )
      ([^bytes bs off  len]
         ))))

from http-kit.

Hi, I look at the code carefully, the reset is threadsafe, should ok.
Can you help by show test case to reproduce the problem?

from http-kit.