Release version 3.1.6

Changes

• Improved journal db trimming to solve disk space problems
• Added trimJournals admin cli command to solve already bad journal situation
  • Look for log messages, you have this problem when you see something like: WARN LatestStore - Failed to deleteMessages toSequenceNr [11115773] for persistenceId [lateststore] due to [null: Circuit Breaker Timed out.]. It means the automatic cleaning cannot handle the amount of data in the clean step.
  • Take the sequence numbers from these warnings and use the trimJournal to start with smaller chunks and end with the amount in logs, otherwise you might remove still required data.
  • Example automation: for x in $(seq 1 110); do echo trimJournal HierarchyStore "$x"77656 | nc -q 3 localhost 8180; sleep 60s; done
• Misc bug fixes

File to choose:

• o-mi-node-x.y.z.zip for Windows, standalone package.
• o-mi-node-x.y.z.deb for Ubuntu, Debian or other Linux with dpkg
• o-mi-node-x.y.z.rpm for Red Hat Linux
• o-mi-node-x.y.z.tgz for Mac or Linux, standalone package
• apidoc-x.y.z.zip contains only documentation