Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
It is possible for a client's queue to leak and never be removed from the ClientRegistrationEventQueueManager's collection, which will result in it collecting events indefinitely and ultimately cause an OOM exception. This can happen if the registration fails for any reason (GII failed due to a peer crashing, unforseen serialization issues while copying the queue, etc). If the client does not retry on the same server after failure, the queue will leak. This is because we currently only remove the queue once a successful registration is performed, but its possible the client will just go to a different server on its next attempt.
