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. Copy anything of yours inside the /webapp/flux/ directory, including your workflow version history in /webapp/flux/vcs, to a directory outside the Flux installation.
  5. Delete the flux directory inside the /webapp/ directory.
  6. Copy the flux.jar and flux.war files from the new release over your existing ones (i.e., /flux.jar and /webapp/flux.war).
  7. Copy the contents of the lib directory from the temporary directory into your existing /lib/ directory.
  8. Copy the .sh files, and on Windows the .bat files, from the new release over your existing ones. If you changed setenv.sh or setenv.bat, note your settings first and reapply them to the new file.
  9. Ensure your Flux 8.4 license key file is in the Flux directory.
  10. Run the configure.sh script (configure.bat on Windows) once. It deletes and rebuilds the /webapp/flux/ directory.
  11. Restore your workflow version history and your own files: copy the contents of your saved vcs directory into the rebuilt /webapp/flux/vcs directory, and put any other files of yours back in the same places. Do not copy the entire old flux directory over the rebuilt one, and do not delete or replace the rebuilt vcs directory.
  12. 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. From Flux 8.4.2 the viewer requires a signed-in Operations Console session, and any signed-in console user can view the files these two entries select; see the Flux 8.4.2 notes below. Only the account that runs Flux should be able to write to the logDir directory.

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.2 (17 November 2026)

Flux 8.4.2 is a maintenance release with security updates to bundled libraries and fixes to the engine, Operations Console and start scripts. 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 runs on Java 8, 11, 17 and 21.

Before upgrading

  • Flux 8.4.2 is not a drop-in replacement. Follow the upgrade steps at the top of this page and, before copying the new files, delete the jetty and lib/aws-s3 directories, lib/bcprov-jdk15on-164.jar and lib/bcpkix-jdk15on-1.64.jar. Then also copy the jetty directory from this release. Otherwise the old libraries stay in use and SMB file actions fail.
  • If you use Windows services, replace the service/windows/lib directory and the wrapper.jar and wrapperApp.jar files in service/windows with the copies from this release. Keep your customized .conf files. Existing services keep their names.
  • From 8.4.0 you can upgrade directly. The 8.4.1 notes below also apply; in addition, delete log4j-api-2.19.0.jar and log4j-core-2.19.0.jar from lib and reports/lib, and reports/lib/commons-beanutils-1.10.1.jar.

Fixes and library updates

  • Jetty: updated the Operations Console’s web server from 9.2.10 to 9.4.58.
  • Amazon S3: updated the AWS SDK from 1.11.617 to 1.12.261.
  • BouncyCastle: updated from 1.64 to 1.85.
  • Jettison: updated from 1.3 to 1.5.4.
  • Windows service: updated bundled Commons Text from 1.6 to 1.10.0.
  • Operations Console: the real-time log viewer now requires a signed-in console session, so it is unavailable when engine security is off, and remote viewing over SSH has been removed. A reverse proxy must preserve the browser’s Host header. Keep the console accessible only from trusted networks.
  • Clustering: fixed cluster joining and Engine.dispose() on Java 17 and 21. An engine that cannot join its cluster now fails to start.
  • Engine configuration: logger types and the audit-trail filter are no longer lost when a configuration is read remotely or from the repository. Re-save any configuration saved on 8.4.0 or 8.4.1.
  • Business calendars: fixed a one-hour shift of included and excluded days on daylight-saving transition days in other time zones, and firings missing from the Time Expression Tester.
  • Client API: workflow listings through a client connection no longer stop at 100. Java client applications need the 8.4.2 flux.jar.
  • Designer: workflow names containing * ? % _ . are now refused. Rename existing files that use them with Save As.
  • Start scripts: the Java version check now uses JAVA_HOME, and start-engine reminds new installations to run configure.

Remaining legacy dependencies

The Operations Console, reporting tool, and Windows service wrapper still include commons-lang-2.6.jar, and the reporting tool still ships older BouncyCastle and Jackson libraries. Vulnerability scanners may continue to flag them.

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.