Hi Alberto,
I don't really know if this change is good or bad but I do have some
thoughts about logging and changing behavior like this.
First off, we might think about whether or not logging these warnings is
currently expected behavior. Would removing/changing it cause surprise for
any users up
Hi,
I'm trying to find the other slow client socket leak. Is it possible
that the socket sometimes not closed for this condition?
[warn tid=324]
ClientHealthMonitor: Unregistering client with member id
...,connection=1,durableAttributes=DurableClientAttributes[id=xxx;
timeout=86400]) due to: The
