Release Notes

All updates are cumulative of all prior updates. Updates are distributed as zip files. Follow these directions to apply the update. To upgrade to Flux 8.4, you must be using an 8.1, 8.2, or 8.3 release.

  1. Shut down any Flux engine and Operations Console instances that are running.
  2. Download and extract the new Flux version to your system. Download the .zip version of the release from support.flux.ly.
  3. Unzip the downloaded zip file to a temporary directory.
  4. Delete the flux directory inside the /webapp/ directory.
  5. Copy the flux.jar and flux.war files from the new release over your existing ones (i.e., /flux.jar and /webapp/flux.war).
  6. Copy the lib directory from the temporary directory into /lib/ directory>
  7. Copy the .sh files from the new release over to your existing one.
  8. Ensure your Flux 8.4 license key file is in the Flux directory.
  9. Run the configure.sh script.
  10. Restart your engines and web application.

After installing Flux, you can optionally enable the real-time Flux Log File Viewer by adding the following entries to the opsconsole8.properties file located in the /.flux/opsconsole8.properties and restarting the Flux operations console webapp.

logDir=/logs logFilter=*.log That’s it! Your new Flux version is now installed and ready to run.

Note: Flux 8.4 requires a JDK, not just a JRE.

Flux 8.4.1 (16 September 2026)

Flux 8.4.1 is a maintenance release with a SQL Server workflow fix and updates to bundled libraries. Download it from the Flux Support Portal. Use your existing Flux 8.4 license key. Flux 8.4 requires a JDK, not just a JRE, and supports Java 17 and 21.

Before upgrading

  • If you maintain a custom config/log4j2.properties, list every defined appender in its appenders= property. The shipped configuration now uses appenders=console,rolling. Log4j 2.25 rejects an unlisted appender, which prevents the engine from starting.
  • H2 remote access has been removed: the engine no longer starts the H2 TCP server on port 9092, and the Operations Console no longer exposes the H2 web console at /console/. Tools using those endpoints must be updated. The engine still uses H2 internally.
  • Replace the Windows service and reporting libraries with the copies from this release if you use those components. Updating only flux.jar will not update their bundled libraries.

Fixes and library updates

  • SQL Server: fixed an unbalanced parenthesis in the ready-workflow query that caused Incorrect syntax near the keyword 'ORDER' and prevented workflows from running. The regression affected 8.3.2 and 8.4.0. No database schema change is required.
  • Derby: updated the embedded database from 10.14.2.0 to 10.14.2.1, built from the Apache 10.14 branch with the LDAP authentication bypass fix. The database format and API are unchanged.
  • Log4j: updated the engine and reporting libraries from 2.19.0 to 2.25.5 and corrected the shipped appender configuration.
  • Windows service: updated bundled Netty from 4.1.36 to 4.1.138 and Commons Lang 3 from 3.8.1 to 3.18.0.
  • Commons BeanUtils: updated the copy embedded in flux.jar from 1.10.1 to 1.11.0.
  • Commons Lang: updated the copy embedded in flux.jar to 3.18.0.
  • H2: updated the embedded database from 1.4.191 to 2.2.220 and removed the obsolete MVCC=TRUE option.

Remaining legacy dependency

The Operations Console, reporting tool, and Windows service wrapper still include commons-lang-2.6.jar. Their Velocity, JasperStarter, and Castor dependencies require the Lang 2 API. Vulnerability scanners may continue to flag those copies; the upgraded Lang 3 copy in the engine does not replace them.

Flux 8.4 (11 July 2025)

  • Flux 8.4 adds support for Java 17 and 21.