The Flux 7.9.15 maintenance release is now available! This release includes 2 improvements and 30 bug fixes.

Flux 7.9.15 is a drop-in replacement for any Flux 7.9.x version.

Improvements

• The file transfer buffer size has been increased from 8k to 50k, improving file transfer performance.
• The Web-based Designer now supports the Message Type property for JMS Actions.

Bug Fixes

• Jobs no longer stop running across the cluster if one engine displays the error message ‘primary flow of control has stopped due to an error condition’.
• Runtime substitution now works correctly for namespaces that are more than one level below the root.
• The Database Stored Procedure Action property “Parameters” can now be set and viewed in the Web-based Designer.
• Flow charts no longer run out of priority order if one flow chart is finishing execution, a high-priority flow chart has a namespace with a lower alphanumeric value than the finishing flow chart, and a lower-priority flow chart has a namespace with a higher alphanumeric value than the finishing flow chart.
• Resuming a PAUSED flow chart now correctly allows the flow chart to begin running again, and the error “unable to seal” is no longer displayed in the logs after resuming.
• The error message “The Flux engine’s primary flow of control is alive, but it is blocked or deadlocked and cannot make progress.” is no longer logged when the engine is operating normally but the SYSTEM_DELAY and FAILOVER_TIME_WINDOW configuration options are both larger than 3 minutes.
• Engines no longer encounter the error NullPointerException when executing flow charts that contains splits and joins.
• Disposing a Flux engine no longer logs the error message “The ENGINES_CACHE Cache is not alive”.
• The Flow Chart Action no longer fails with the message “Repository Element is not a flow chart”.
• While the flow chart cache is enabled, multiple flow contexts in the error state of the same flow chart no longer produce a “could not find action” error message when attempting to execute the default error handler.
• The Rest Action now gracefully shuts down all HTTP Connections after executing, preventing connections from remaining open unnecessarily (this behavior was not known to have any negative impact on the Flux system or flow chart execution).
• Flow chart namespaces that contained both a capital letter and a space character in a branch name no longer bypass their concurrency throttle settings in the runtime configuration.
• The auto-refresh option on the Flow Charts page of the Operations Console now correctly loads updated data.
• Attempting to look up users on an engine no longer fails with an error when the engine is configured to use the PostgreSQL database.
• The File Create Action no longer produces an exception in the Flux logs upon successful execution.
• File triggers no longer produce an error if the base directory is not present when using an FTP, FTPS, or SFTP host.
• The built-in Windows services now correctly use the recommend JVM settings when running Flux.
• The error message ORA-00918: column ambiguously defined no longer appears while an engine is selecting flow charts for execution.
• Flow charts with a namespace containing an escaped HTML character now correctly accept commands (like pause, resume, or remove) from the Operations Console.
• The error java.lang.NullPointerException no longer appears if a JMS Inbound Configuration fails to register with the engine on engine startup.
• If a flow chart is created with the “Paused” property enabled, it no longer becomes paused again at the next transaction break.
• The engine now correctly recovers and connects to a database if the database was not available when the engine started, but the database becomes available later.
• The REST Action property “Request Entity String” is now editable in the Web-based Designer.
• Flow Chart Actions no longer encounter the error message “You must be logged in to call this method” when LDAP security is enabled on the engine.
• The error flux.EngineException: Unable to load flow chart from file: null. no longer appears when running a Flow Chart Action when LDAP security is enabled on the engine.
• Java API: The getFlowChartElements(String namespace, SuperState superState, Set<SubState> subStates, String engineName, String actionName, String messageFilter) method now correctly returns results when filtered with SubState.ANY.
• Specifying a base directory of ‘./’ no longer signifies the root of an FTP, SFTP, or FTPS file system. It now implies from the user’s home directory.
• The file transfer monitor now correctly displays the appropriate unit for file sizes larger than 1 MB.
• The Audit Trail Trigger now ignores old audit trail entries in a looping flow scenario.
• JMS Action body property now correctly saves from the Desktop Designer.