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.
