<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>Flux News</title>
    <link>http://blogs.fluxcorp.com/blogs/flux_news</link>
    <description>Flux News</description>
    <pubDate>Sat, 17 Nov 2007 00:50:31 GMT</pubDate>
    <generator>Clearspace 1.6.0 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2007-11-17T00:50:31Z</dc:date>
    <item>
      <title>Flux 7.4.4 maintenance release</title>
      <link>http://blogs.fluxcorp.com/blogs/flux_news/2007/11/16/flux-744-maintenance-release</link>
      <description>A maintenance release for Flux 7.4 is now available and includes several bug fixes.&lt;br /&gt;
&lt;br /&gt;
Flux 7.4.4 downloads are available here:&lt;br /&gt;
&lt;a class="jive-link-external" href="http://my.fluxcorp.com/" title="Flux Customer Portal"&gt;my.fluxcorp.com&lt;/a&gt; (for Flux customers)&lt;br /&gt;
&lt;br /&gt;
The latest version of Flux is available from:&lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.fluxcorp.com/download" title="Download an evaluation copy of Flux"&gt;www.fluxcorp.com/download&lt;/a&gt; (for Flux evaluators)&lt;br /&gt;
&lt;br /&gt;
The following maintenance changes were made in this Flux maintenance release, version 7.4.4.&lt;br /&gt;
&lt;br /&gt;
&lt;i&gt;&lt;b&gt;Bug Fixes:&lt;/b&gt;&lt;/i&gt;&lt;br /&gt;
&lt;br /&gt;
1.  A background thread remained active after Engine.dispose() was called, which prevented the JVM from exiting. Fixed.&lt;br /&gt;
&lt;br /&gt;
2.  If a stable period was set on a file trigger, the result set of the trigger would yield no values. Fixed.&lt;br /&gt;
&lt;br /&gt;
3. When the cache type engine configuration option was set to either LOCAL or NETWORKED, an IllegalStateException could occur. Fixed.&lt;br /&gt;
&lt;br /&gt;
4.  Sub flow charts were being displayed as separate flow charts inside the flow charts page of the Operations Console. Fixed.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
9. When Flux was running inside WebLogic, a NullPointerException occurred and the action icons did not display correctly when monitoring a flow chart. Fixed.</description>
      <category domain="http://blogs.fluxcorp.com/blogs/flux_news/tags">flux</category>
      <category domain="http://blogs.fluxcorp.com/blogs/flux_news/tags">maintenance</category>
      <category domain="http://blogs.fluxcorp.com/blogs/flux_news/tags">7.4.4</category>
      <pubDate>Sat, 17 Nov 2007 00:57:10 GMT</pubDate>
      <author>eric</author>
      <guid>http://blogs.fluxcorp.com/blogs/flux_news/2007/11/16/flux-744-maintenance-release</guid>
      <dc:date>2007-11-17T00:57:10Z</dc:date>
      <clearspace:dateToText>16-Nov-2007 17:50</clearspace:dateToText>
      <wfw:comment>http://blogs.fluxcorp.com/blogs/flux_news/comment/flux-744-maintenance-release</wfw:comment>
      <wfw:commentRss>http://blogs.fluxcorp.com/blogs/flux_news/feeds/comments?blogPostID=1031</wfw:commentRss>
    </item>
  </channel>
</rss>

