Twice I observed that when one client aggregate of a shared remote CM crashed with an out-of-memory exception the service stopped responding to the other client's requests. No errors found in the service log. The client was not using the service at the time of the crash. Requests stacked up on the input queue ... almost as if the service was blocked on an empty pool, or ...? Killing a client (cntl-C) did not cause the hang. Weird!