Barry Oglesby

I'm not sure how to resolve the race condition you mention, but I see similar behavior with client/server connections. If a burst of connections is requested and none of those...

I ran a few tests with some extra logging on these changes. They look good. #### The receiver exchanges profiles with the locator: ``` [warn 2022/03/16 14:16:12.440 PDT locator-ln tid=0x50]...

Thats a pretty cool idea. I'm not sure whether the CacheServerMXBean has that behavior, but I guess it could be added. In any event, I think this change is good....