Flux News

Flux 7.7.6 maintenance version released

nickm — Wed, 20 Aug 2008 18:00:22 GMT

A maintenance release for Flux 7.7 is now available and includes four improvements and several bug fixes.

Flux 7.7.6 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.7.6.

Improvements:

(FLUX-463) Made the default engine bind name for the Desktop Designer configurable via a Java properties file.
(FLUX-371) Added support for loading resources from JAR files located in the flow chart's listener class path.
(FLUX-492) Added a configuration option to remove the "remember me" check box when signing into an engine in the Operations Console.

Bug Fixes:

(FLUX-461) If the file_transfer_debug configuration option was set to true and a Secure FTP host was used, the expected debug output would not be generated. Fixed.
(FLUX-430) If a File Not Exist Trigger criteria include used variable substitution and the file limit was set to a value greater than zero, a ClassCastException would occur. Fixed.
(FLUX-457) Transferring files using a Secure FTP host did not work correctly with some Secure FTP servers. Fixed.
(FLUX-454) Cluster networking utilized the User Datagram Protocol (UDP) when configured to use the Transfer Control Protocol (TCP). Fixed.
(FLUX-203) If a flow chart was resubmitted to the engine soon after completing execution, an EngineException would occur. Fixed.
(FLUX-495) Agents registered to an engine would fail to re-register if the engine was restarted. Fixed.
(FLUX-343) The SQLException was not logged when Flux obtained an invalid database connection. Fixed.
(FLUX-496) When running Flux against Sun JDK 6, cluster networking did not work correctly and the log displayed the error message "Unable to initalize the Flux network cache". Fixed.
(FLUX-486) If an agent encountered an error while running a Process Action, a NullPointerException could be thrown. Fixed.

Flux 7.5.3 maintenance version released

nickm — Thu, 29 May 2008 20:23:41 GMT

A maintenance release for Flux 7.5 is now available and includes one improvement and several bug fixes.

Flux 7.5.3 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.5.3.

Improvements:

Flow charts names are now case-sensitive in order to reduce database deadlocks. WARNING: This could have a negative impact on your application. Please test and make appropriate changes.

Bug Fixes:

The Flux engine could become blocked and cease processing jobs under a heavy load. Fixed.
Confirming a Business Process Trigger on a stopped engine would result in a NullPointerException. Fixed.
All engines running in the same JVM logged to the same log file. Fixed.
Using an unsupported XML parser would display XML errors to the engine console. Fixed.
Icons indicating the state of engines in the engines page of the Operations Console were sometimes incorrect. Fixed.
Clicking a flow chart in the flow charts page of the Operations Console
could cause a JavaScript error when using a secure engine. Fixed.
A File Move Action using multiple Simple File Target Criteria would only move files to the first target criteria. Fixed.
Running a flow chart with a checkpoint (a flow that publishes messages)
could cause a message iterator to close prematurely. Fixed.
JavaScript exceptions occurred when embedding the Web-based Designer as a JavaScript widget. Fixed.
A NullPointerException could occur when removing a running sub flow chart. Fixed.
A ClassCastException occurred when editing action variables in the Web-based Designer. Fixed.
An EngineException occurred when running the software developer's security example. Fixed.
Regular expression special characters were not allowed inside variable values when using substitution. Fixed.
A NullPointerException occurred when attempting to access the
Web-based Workflow Designer of the Operations Console on an engine
configured to use external security. Fixed.
A NullPointerException occurred when accessing the security page of the
Operations Console on an engine configured to use external security.
Fixed.
When using a UNC file host, regular expression excludes were not working properly. Fixed.
An exception occurred when using a Process Action in a sub flow chart with an agent pool defined. Fixed.

Flux 7.7.4 maintenance version released

nickm — Wed, 28 May 2008 19:53:58 GMT

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

Flux 7.7.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.7.4.

Bug Fixes:

In the Operations Console, applying a filter to the Flow Charts page did not work properly. Fixed.
Running a flow chart with a checkpoint (a flow that publishes messages) could cause a message iterator to close prematurely. Fixed.
Agents and Engines with cluster networking enabled would not dispose correctly. Fixed.
Regular expression special characters were not allowed inside variable values when using substitution. Fixed.
A Class Cast Exception would occur if a flow chart containing a runtime data map was exported to the engine. Fixed.

Flux 7.6.2 maintenance version released

eric — Wed, 16 Jan 2008 21:23:05 GMT

A maintenance release for Flux 7.6 is now available and includes two improvements and several bug fixes.

Flux 7.6.2 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.6.2.

Improvements:

A new error flow condition, ERROR_WITHOUT_ROLLBACK, has been added
to prevent the rollback of a transaction upon execution of an error
flow.
Added buttons to the messaging pages of the Operations Console for removing all publishers and messages.

Bug Fixes:

A ClassCastException occurred when using the Flux engine Spring Bean from the Spring Modules project. Fixed.
The expected file sets were not returned when using certain wildcards in a remote host's includes. Fixed.
When a file trigger fired, if one file matching the trigger's file criteria was found and that file had reached its file stable period, all files that otherwise matched the file criteria were returned instead of just those matching files whose stable period had been reached. Fixed.
Some of the main navigational menu items were missing when logging into the Operations Console using an embedded fluxwebapp.properties. Fixed.
When dragging a File Not Exist Trigger on to the canvas of the Desktop Designer, an IllegalArgumentException was displayed. Fixed.
Setting the milliseconds field in the Time Expression Editor of the Web-based Designer erased all other cron fields. Fixed.
When multiple flows connected two actions in the Desktop Designer, copying and pasting those flows resulted in the loss of their flow conditions. Fixed.
An IllegalStateException ocurred when exporting a flow chart containing a skippable Error Action to a Flux engine. Fixed.
A NullPointerException could occur when attempting to login to a secure engine in the Operations Console. Fixed.
A "Closed Connection" SQLException could occur when using Flux messaging. Fixed.
The help function in the reports view of the Operations Console was not working. Fixed.
A ClassCastException could occur when using a File Copy or Move Action with a local host as the source criteria, and an FTP Host as the target criteria. Fixed.
The Time Expression section of the Flux manual incorrectly described the "*/2" step value notation as including all even-numbered items in a range, starting from zero. Instead, the notation "*/2" means that every second item in a range is included, starting from the beginning of the range. The documentation was fixed in the Flux manual. No code changes were needed.
An error occurred when attempting to access the help window in the Web-based Designer. Fixed.
The help window in the Web-based Designer was not displaying at the correct height in Internet Explorer. Fixed.

Flux 7.6.1 maintenance version released

eric — Thu, 13 Dec 2007 22:10:41 GMT

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

Flux 7.6.1 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.6.1.

Improvements:

1. Increased the maximum size of flow charts that can be uploaded to the repository from the Operations Console from 5MB to 20MB.

Bug Fixes:

1. An EngineException was thrown when attempting to set the DATA_SOURCE_AUTO_COMMIT_CHECK configuration property in an XML engine configuration file. Fixed.

2. File criteria pairs were not stored when saving a flow chart in the Desktop Designer. Fixed.

3. Email addresses were not saved correctly when editing Mail Actions in the Web-based Designer. Fixed.

4. An error occurred when attempting to drag actions onto the flow chart canvas in the Web-based Designer when using WebLogic with Internet Explorer 6. Fixed.

5. A log4j error message was displayed to standard out when starting an engine. Fixed.

6. An EngineException with a message of "The bean property must be a java.lang.String" was thrown when attempting to save a business process in either the Web-based Designer or Desktop Designer. Fixed.

7. An EngineException with a message of "The bean property must be a java.lang.String" was thrown when attempting to save a business process in either the Web-based Designer or Desktop Designer. Fixed.

Flux 7.4.4 maintenance release

eric — Sat, 17 Nov 2007 00:57:10 GMT

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.

Flux 7.5.1 maintenance release

eric — Sat, 27 Oct 2007 01:59:52 GMT

A maintenance release for Flux 7.5 is now available. Flux 7.5.1 contains one feature improvement to make the Operations Console more responsive when monitoring an engine with thousands of flow charts and several bug fixes.

Flux 7.5.1 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.5.1.

Improvements:

1. The Operations Console's flow charts page displayed an unlimited number of flow charts, causing performance issues. The flow charts page is now limited to 500.

Bug Fixes:

1. A NullPointerException could occur when manually adding a Flux engine to the engines page of the Operations Console. Fixed.

2. In the Operation Console's engines page, a NullPointerException could occur when viewing multiple engines bound to the same RMI registry using separate bind names. Fixed.

3. The database driver class was required to be in the class path upon creation of a Flux Configuration object, not an Engine object. Fixed.

4. The error message diplayed when JBoss Cache could not be initialized was unhelpful. Fixed.

5. The "RESULT.result" flow context variable was case-sensitive when set as the condition on a customized conditional flow out of a Business Process Trigger. Fixed.

6. The DATA_SOURCE_AUTO_COMMIT_CHECK configuration option was not present in the Engine Configuration Document Type Definition (DTD) file. Fixed.

7. When processing a high volume of messages, Message Triggers would fail to consume messages in a timely manner. Fixed.

8. In the Operations Console flow charts page, flow chart action buttons were enabled for sub flow chart actions, even though Flux does not support flow chart actions on sub flow charts. Fixed.

9. 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.

10. 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.

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

12. 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.

13. 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.

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

15. If a flow chart completed execution, and then was resubmitted to the Flux engine soon after, an EngineException would occur. Fixed.

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

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

18. Save and export operations in the Web-based Designer would not function when deploying the Operations Console on a web application context other than root (/). Fixed.

Flux 7.4.3 maintenance release

eric — Tue, 09 Oct 2007 14:07:47 GMT

A maintenance release for Flux 7.4 is now available. Flux 7.4.3 contains one feature improvement to make the Operations Console more responsive when monitoring an engine with thousands of flow charts and several bug fixes.

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

Improvements:

1. The Operations Console's flow charts page displayed an unlimited number of flow charts, causing performance issues. The flow charts page is now limited to 500.

Bug Fixes:

1. The start of run property was dynamically set on the start action of a flow chart by Flux, even if the end of run action could not be determined. Fixed.

2. Pre-scripts were only executed once per trigger, instead of once per trigger for each flow context. Fixed.

3. Select inputs on the Reports page would show through the Report Details pane of the Operations Console in Internet Explorer 6. Fixed.

4. Certain engines were not being displayed on the engines page of the Operations Console. Fixed

5. When a flow chart completed, the flow chart would not be removed from the database until 23:00. Fixed.

6. The "RESULT.result" flow context variable was case-sensitive when set as the condition on a customized conditional flow out of a Business Process Trigger. Fixed.

7. A NullPointerException could occur when manually adding a Flux engine to the engines page of the Operations Console. Fixed.

8. In the Operation Console's engines page, a NullPointerException could occur when viewing multiple engines bound to the same RMI registry using separate bind names. Fixed.

9. The error message diplayed when JBoss Cache could not be initialized was unhelpful. Fixed.

10. In the Operations Console flow charts page, flow chart action buttons were enabled for sub flow chart actions, even though Flux does not support flow chart actions on sub flow charts. Fixed.

11. The database driver class was required to be in the class path upon creation of a Flux Configuration object, not an Engine object. Fixed.

12. When processing a high volume of messages, Message Triggers would fail to consume messages in a timely manner. Fixed.

Flux 7.4.3 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)