Trimmomatic 0.40 consistently throws a Java OutOfMemoryError during the trimming/trim-stats step when JAMS runs with high thread counts (e.g., -threads 56). This results in estreadlength = NA and JAMS reports 0 bases for assembly.
Reverting to Trimmomatic 0.39 fixes the issue.
TODO:
Investigate whether we should (a) cap trimming threads, (b) pass an explicit JVM -Xmx, or (c) recommend 0.39 until 0.40 is tested with JAMS.