Flux 7.9.9 maintenance release

A maintenance release for Flux 7.9 is now available and includes twenty-two bug fixes and four improvements.

Flux 7.9.9 download 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 release, version 7.9.9.

Improvements:

1. For long-running actions, database connections are now queried every three minutes to prevent database timeouts while the actions are running.
2. Added the ability to specify an admin username for the cluster (in addition to the existing cluster password) to specify which user account the web app should use when looking up information for the connected engines.
3. If a flow chart is interrupted, it will now continue to run on the same engine when it resumes execution (previously, it could run on any available engine in the cluster).
4. Reduced the volume of log messages and audit trail events that occurred when the Operation Console detected engines.

Bug Fixes:

1. High memory usages could occur when executing actions and triggers that had timeouts set a long while in the future. Fixed.
2. If the Operations Console attempted to connect to an engine using external security (such as LDAP), a NotSerializableException could occur that would make the engine inacessible from the Console. Fixed.
3. If an action was monitoring for a signal, executed in a loop in a flow chart, and the action name was mixed-case, the signal would not be cleared when the flow chart looped back to continue execution. Fixed.
4. If three engines were running in a cluster and one of the engines was disposed using the Java API, the flow charts running on that engine were not failed over correctly. Fixed.
5. In Web-based Designer, FileAction containing an UNCHost in a FileCriteria would fail to save to the repository causing an EngineException for null port value. Fixed.
6. If variable substitution was used in the include of a File Action with a file criteria host and target, the substitution would only be evaluated on the first execution of a looping flow context. Fixed.
7. On FlowChartElement objects returned from a FlowChartElementIterator, calls to getStartOfRun() or getAverageRuntime() would always return null. Fixed.
8. After searching the audit trail on a remote engine, the engine could become deadlocked and stop executing flow charts. Fixed.
9. When running a process on an agent with multiple Flux engines in a clustered environment, the agent’s work would be wrongly failed over and re-executed. Fixed.
10. If a Process Action ran on an agent, it would log multiple Entering Action and Executing Action events to the audit trail. Fixed.
11. In the Mail Action, when the setToAddresses(), setCcAddresses(), or setBccAddresses() methods were called, email address arguments were appended to the existing list of email addresses instead of replacing them. Fixed.
12. If a flow chart contained a split, the branching flow contexts could be prematurely failed over if they ran longer than the failover time window. Fixed.
13. When a large number of flow charts were executing on an engine, triggers would not time out quickly even when their timeout expression was satisfied. Fixed.
14. When executing a process on an agent that runs longer than three minutes, the process would be failed over and re-executed. Fixed.
15. Flow charts would not execute on any engine in a cluster if one engine’s concurrency throttles were at capacity. Fixed.
16. When using a Database Condition Action or Trigger, if flow of control returned to that action or trigger, or the condition was not met on the first execution, the action would fail with a connection closed exception. Fixed.
17. The engine column of the flow charts page in the Operations Console always displayed the name of the engine that the user was connected to in the Operations Console. Fixed.
18. Editing a FlowChart containing a RestAction from the repository in Operations Console and saving it back to the repository would fail with EngineException. Fixed.
19. A ClassCastException could occur when calling Engine.getFlowChartElements() on a secure engine. Fixed.
20. If a secured engine was configured to use a JAAS login module, attempting to run a Flow Chart Action would fail with the message “user must be logged in to call this method”. Fixed.
21. On a secured engine, users could not publish messages from the Operations Console, even when Message Administrator permissions were enabled. Fixed.
22. Process Actions that run on agents are displayed multiple times in run reports. Fixed.

Flux 7.9.8 maintenance release

A maintenance release for Flux 7.9 is now available and includes seventeen bug fixes and six improvements.

Flux 7.9.8 download 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 release, version 7.9.8.

Improvements:

1. Enhanced Mail Action to support Gmail as an SMTP provider.

2. Added support for multipart form processing, HTTP headers, and SSL certificates in Rest Action.

3. The Database Stored Procedure Action now reports the out parameters from its result to the audit trail, allowing them to be viewed in the Operations Console.

4. Improved the error message for attempting to create a runtime configuration node when a node already exists with the same name.

5. The log message: “No matches were found for the path” was logged at the WARNING level instead of the correct FINE level. Fixed.

6. Added support for persisting variables larger than 10,000 bytes when using the in-memory database.

Bug Fixes:

1. When running secured engines in a cluster, only flow charts running on the same engine the user was connected to could be interrupted. Fixed.

2. If the File Delete Action could not find a specified include, it would issue a bad delete command to the server, incorrectly causing the action to fail. Fixed.

3. Restarting engines in a cluster could prevent flow charts from executing. Fixed.

4. An out of memory exception would occur do to a memory leak in long running Flux environments. Fixed.

5. When using a runtime configuration file, if a concurrency throttle of 1 was specified on the root of the runtime configuration tree, the throttle would be ignored. Fixed.

6. The SQLException: “Closed Statement” occurred when using the Database Stored Procedure Action to call a stored procedure that returned output parameters. Fixed.

7. If date substitution was used in the base directory property of a file criteria on a file action, the date substitution would fail to reset after the first loop in a looping flow context. Fixed.

8. Message Triggers awaiting assignment of a message would sometimes have to wait up to the system delay before message assignment occurred. Fixed.

9. If an agent was restarted while connected to an engine, the engine would display the agent’s status as “STOPPED” and would not submit any new work to that agent. Fixed.

10. The Flux Desktop Designer failed to open a flow chart that included a timer trigger with an invalid time expression. Fixed.

11. A SQLException could be thrown when using the Oracle 11gR2 JDBC driver. Fixed.

12. When two RMI engines are created in the same JVM which uses the same RMI port, the second engine would fail to create with port in use exception. Fixed.

13. When an engine’s flow chart selection became stuck, no other engines in the cluster would continue selection. Fixed.

14. If a file action that used a UNC host encountered an exception, the default error handler was not invoked. Fixed.

15. The Flux Web Application start-up script was not working properly in a Linux/Unix environment. Fixed.

16. Factory.lookupCluster() APIs threw a NullPointerException when invoked. Fixed.

17. The forecast page of the Operations Console only displayed the next scheduled trigger date, and not all forecast firings for the specified time frame. Fixed.

Flux 7.7.19 maintenance release

A maintenance release for Flux 7.7 is now available and includes six bug fixes.

Flux 7.7.19 downloads are available from the Flux Portal:

my.fluxcorp.com

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

Bug Fixes:

1. When using an FTP, SFTP, or FTPS host, the URLs generated by Flux did not use the “%2F” syntax for specifying a file from the root directory of a server. Fixed.
2. Duplicate values were added to the HAS_RUN_PRESCRIPT variable when using a trigger in a flow chart. Fixed.
3. Action.removeFlow() would always return false, even if the flow was successfully removed. Fixed.
4. If an engine had security enabled but was using a non-default login module (such as LDAP), variable substitution would fail for any variables in the runtime configuration. Fixed.
5. When upgrading from Flux 7.7 (or lower) to Flux 7.8 (or higher), any flow charts that used the “Sort Order” file criteria property would cause an InvalidClassException. Fixed.
6. An IllegalArgumentException could be encountered occasionally when using the Desktop Designer. Fixed.

Flux 7.9.7 maintenance release

A maintenance release for Flux 7.9 is now available and includes two bug fixes and four improvements.

Flux 7.9.7 downloads are available from the Flux Portal:

my.fluxcorp.com

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

Improvements:

1. Information about engines listed in the Operations Console is now retrieved asynchronously to eliminate delays when logging into the Operations Console.
2. When Flux lost database connectivity, a high number of database connection requests would be issued. Flux now waits 30 seconds before attempting to retrieve a connection.
3. Added external database support for database actions, allowing them to use databases other than the one the Flux engine is using.
4. Improved the error message to display the specific cause when Flux fails to create an RMI engine.

Bug Fixes:

1. Duplicate values were added to the HAS_RUN_PRESCRIPT variable when using a trigger in a flow chart. Fixed.
2. The system resource command only worked on the first engine started in a cluster. Fixed.

Flux 7.9.6 maintenance release

A maintenance release for Flux 7.9 is now available and includes twelve bug fixes.

Flux 7.9.6 download are available here:

my.fluxcorp.com (for Flux customers)

The following maintenance changes were made in this Flux release, version 7.9.6. If you are migrating File Triggers with the “sort order” property set, it will default to FILENAME_ASCENDING after the migration. Please make sure to update the “sort order” property if you have changed the default value in your File Triggers.

Bug Fixes:

1. (FLUX-890) When using an FTP, SFTP, or FTPS host, the URLs generated by Flux did not use the “%2F” syntax for specifying a file from the root directory of a server. Fixed.
2. (FLUX-889) A NullPointerException could occur when using a Simple File Source/Target with a UNC host and no user information. Fixed.
3. (FLUX-884) When upgrading from Flux 7.7 (or older) to Flux 7.8 (or higher), a UNC host file criteria that used the “Port” property could cause an IllegalArgumentException on the engine. Fixed.
4. (FLUX-882) The Mail Action methods setToAddresses(), setCcAddresses(), and setBccAddresses() did not support an array created from Arrays.asList() as an argument. Fixed.
5. (FLUX-880) A secure engine would not dispose cleanly when Engine.dispose() was called. Fixed.
6. (FLUX-879) Starting an agent from the command line would print “null” to the console and fail to show the startup message. Fixed.
7. (FLUX-878) Action.removeFlow() would always return false, even if the flow was successfully removed. Fixed.
8. (FLUX-875) Attempting to claim a Business Process Trigger on an engine configured to use PostgreSQL would throw an exception. Fixed.
9. (FLUX-870) When using an empty base directory on a file criteria with an FTP, SFTP, or FTPS host specified, a NullPointerException would occur. Fixed.
10. (FLUX-820) The engine could stop executing flow charts and prevent connections from remote clients, including the Flux Operations Console. Fixed.
11. (FLUX-673) When upgrading from Flux 7.7 (or lower) to Flux 7.8 (or higher), any flow charts that used the “Sort Order” file criteria property would cause an InvalidClassException. Fixed.
12. (FLUX-147) An IllegalArgumentException could be encountered occasionally when using the Desktop Designer. Fixed.