Unexpected shutdown after upgrade to play framework 3.0 with ServerStoppedReason

103 Views Asked by At

We just upgraded to Play Framework 3.0 with Pekko and some of nodes in production are shutting down randomly with the message

Starting synchronous coordinated shutdown with ServerStoppedReason reason and 2147513000 milliseconds timeout.

However, there's no explanation of what is triggering the shutdown. Is there any way to get more information about what's triggering the shut down? It's only happening to a subset the subset of our nodes that run some background Pekko actors in addition to the request handling, but ServerStoppedReason is a play signal so it seems like this must be coming from Play.

My original thought was maybe it was memory related, but reducing the memory limits actually caused it to happen less often. And I would expect to see some sort of error message if it was a memory issue (which I do when I turn the memory down low enough that it immediately crashes). Any ideas?

0

There are 0 best solutions below