> HTTP-BOSH-XMPP (like JWChat, JsJAC)?
> In idle state of connected client, I see a leak of socket descriptors.
> Those sockets are hanging in CLOSE_WAIT state, and soon descriptor are
> exhausted causing yaws crash and session break.
> Some info:
> request directly to host(port) of BOSH server, which is differ from
> web-page's host.
> state, response is absent and client repeats request after client timeout.
> 3) yaws keepalive_timeout is a bit longer then client timeout to save
> BOSH session.
> Have anybody resolved this issue with CLOSE_WAIT sockets?
> Or, could it be a problem with OS settings?
> Or, could it be a bug in revproxy implementation?
> Any thoughts?
The rev_proxy code is experimental. I think some have used it
successfully but YMMV.
Klacke and I recently chatted about this code. He has no time to work
on it at present, and I don't have any use cases for it myself that
would help me improve it. However, if people are willing to submit
test cases for it, especially cases that should work but don't, I'd
definitely fix any problems those cases cover.
Andrew, any chance you could whittle your code down to a minimal test
case that shows the problem?