We encountered the memory leak being described (the client map in
HttpTunnelServlet). In our case, we had an HTTP-based network of brokers on
an unreliable network. The brokers would constantly reconnect to each other
and eventually the client map caused an OOM.
I've reported the issue and incl
Well it's been quite a long time and this is still an issue.
Is there any progress going on with this I'm having lots of problems with
HTTP transport and this is one of them.
TimDog wrote:
>
>
> Actually for a broker connection, RegionBroker is the class that's
> refusing to allow the connecti
Well, seeing as how this message went unanswered for so long, I decided to
crack open the source. Might as well help all those who might have a
similar question in the future.
I'm going to call it a bug. There's a Map in HttpTunnelServlet that maps
clientID's to BlockingQueue transport objects.
