If you are getting an OOME there are some JVM flags that can help dump an error file or heap dump, or run arbitrary commands when an error occurs:
-XX:ErrorFile=./hs_err_pid<pid>.log -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=./java_pid<pid>.hprof -XX:OnError="<cmd args>;<cmd args>" -XX:OnOutOfMemoryError="<cmd args>;<cmd args>" That might help you determine the cause if it is an error condition. On Tuesday, March 7, 2017 at 3:25:52 PM UTC-6, piastkra...@gmail.com wrote: > > I asked the same question a year ago. The problem was that I was getting > an OutOfMemoryError. This is an Error but it is not an Exception. If you > catch all Exceptions, you will still not catch the OutOfMemoryError. You > have to catch that too. > > > > On Tuesday, March 7, 2017 at 2:54:26 PM UTC-5, Kevin Corcoran wrote: >> >> On Mon, Mar 6, 2017 at 11:56 PM, JokkeB <jahv...@gmail.com> wrote: >> >>> After adding this, I still can't see an exception before the app dies. >>> >> >> I've encountered this before when the Linux "OOM killer" kicks in, which >> is especially likely if you are running your application on a >> resource-constrained system (say, a VM with a low RAM allocation) or your >> application is competing with other programs for memory. >> >> -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
