I just looked at the image and there were bunch of processes hung up on one or another of two critical blocks; although it did not appear that either was part of the call stack of the other. One of them was using a Semaphore instead of a Mutex, so that is suspicious. There were so many, it wasn't evident what the root cause of the issue was, so I decided to bounce the server and will monitor it over the next days to see if the issue returns. On Fri, Dec 30, 2016 at 2:34 AM, Fabio Niephaus <[hidden email]> wrote:
|
2016-12-31 0:15 GMT+01:00 Chris Muller <[hidden email]>:
Could it be related to the timeout we experiment each time we commit a package?
|
It could be. I never experienced the timeout myself, so wondered whether it was doing a GC at that moment. It could have been this.. |
Free forum by Nabble | Edit this page |