Hi everyone,
We saw strange behaviour , as broker stopped accepting connections and client start receiving Connection Already Closed or Topic not available exceptions. The broker java process itself is up and running, but curl http ports such as curl broker metrics stop return anything. It is only works when we restart the broker again , however, I was able to reproduce the issue by a simple java program which kerp looping to open new socket to the broker port without closing the socket on every loop. So after a while the clients start to get that connection already closed exceptions. So it seems as connection leak as it keeps alive. Would you please advise how to fix that issue? Thanks and best regards Tamer
