Thanks Joe, I am getting the general opinion that on OOM restart is not optional, must be done. In that case I am going to also look at some of the following
-XX:+ExitOnOutOfMemoryError -XX:+CrashOnOutOfMemoryError ExitOnOutOfMemoryError When you enable this option, the JVM exits on the first occurrence of an out-of-memory error. It can be used if you prefer restarting an instance of the JVM rather than handling out of memory errors. CrashOnOutOfMemoryError If this option is enabled, when an out-of-memory error occurs, the JVM crashes and produces text and binary crash files. Best Regards John > On Dec 3, 2020, at 10:09 AM, Joe Witt <joe.w...@gmail.com> wrote: > > John, > > First, as a general rule it is usually very doable to build flows which are > very stream oriented rather than entire file oriented. That processor by its > nature isn't friendly in this way if configured to work with large memory > chunks. Alternatives often exist. > > Second, I do think it is wise to restart the JVM in the event of an OOME. > There are ways to configure your JVM to do this automatically. Googling > 'restart JVM on oome' for instance could be helpful there. > > Thanks >
