problem

The messagebus server does not respond to new connections and consumes one CPU core with nearly 100%.

reason

In seldom circumstances it can happen that the processing of a session resync is causing an endless loop. The concrete reasons are unclear, it must be in conjunction with long running browser windows, automatically deleted sessions (garbage cleanup) or a messagebus restart. The details are unclear.

solution

The concrete problem of the endless loop was that a queued message was removed from the queue and was processed. In processing the message it could happen that it was added again to the queue - while we are still in the loop processing the queue. So the endless loop was triggered.

This is changed now by operating on a clone of the queue and resetting the shared queue instance.