This SO questions lists a few alternatives about how to achieve that with a reasonably new JVM:
http://stackoverflow.com/questions/12096403/java-shutting-down-on-out-of-memory-error On Wednesday, February 22, 2017 at 11:27:21 AM UTC+1, Hippolyte Léger wrote: > > Hello, > so I have a fairly large actor system on several nodes using akka-remote > and a bit of a congestion problem. From time to time, some actors are > overflown with messages and I get the infamous GC overhead OOM error. > The problem is, when it happens the akka application doesn't stop, it > keeps logging the OOM error trace again and again for hours, and I have to > manually stop the process, which is a real pain since I cannot do automated > experiments. > Is there a way to catch this error and stop the application immediately? > That would be really nice. > > Thank you for your help, > Hippolyte > -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
