A maintenance release for Flux 7.4 is now available and includes several bug fixes.

Flux 7.4.4 downloads are available here:
my.fluxcorp.com (for Flux customers)

The latest version of Flux is available from:
www.fluxcorp.com/download (for Flux evaluators)

The following maintenance changes were made in this Flux maintenance release, version 7.4.4.

Bug Fixes:

1. A background thread remained active after Engine.dispose() was called, which prevented the JVM from exiting. Fixed.

2. If a stable period was set on a file trigger, the result set of the trigger would yield no values. Fixed.

3. When the cache type engine configuration option was set to either LOCAL or NETWORKED, an IllegalStateException could occur. Fixed.

4. Sub flow charts were being displayed as separate flow charts inside the flow charts page of the Operations Console. Fixed.

5. When running a Process Action in synchronous mode, with Agents enabled, the agent result took a substantial amount of time to report back to a Flux engine. Fixed.

6. The indicator for the currently executing action in the real time monitor of the Operations Console failed to stop when the action stopped execution. Fixed.

7. If a sub flow chart failed, the parent flow chart was not able to be recovered through the Operations Console's flow charts page. Fixed.

8. After deploying Flux inside a WebLogic server, a "java.sql.SQLException: Result set already closed" exception would occur when browsing to the flow chart's page of the Operations Console. Fixed.

9. When Flux was running inside WebLogic, a NullPointerException occurred and the action icons did not display correctly when monitoring a flow chart. Fixed.