<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 21/09/2010 13:02, Thomas Peuß wrote:
<blockquote
cite="mid:1458220EF3BF0A44B6606275868BF106AC57AB@nterra-serv3"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="MS Exchange Server version
6.5.7652.24">
<title>Drools Fusion High Availability</title>
<!-- Converted from text/plain format -->
<p><font size="2">Hello!<br>
<br>
We are thinking about using Drools Fusion 5.1 for Complex
Event Processing. We have a prototype running that consumes
events from a Tibco JMS server. Everything works as expected.
My boss is now asking about HA features that are available. I
have read the documentation and found nearly nothing about HA
features. In the case of Fusion you have long running threads
working on fireUntilHalt(). So when the node goes down you
loose all the events that live in the ksession memory. What
possibilities do you see to run Fusion in an HA environment?<br>
</font></p>
</blockquote>
There are two bespoke solutions you can do.<br>
1) Setup 2 or more engines and the JMS queues sends facts to both so
that you have redundancy.<br>
2) Keep all facts in a HA cloud, using something like infinispan, if
the engine goes down restart it and reload the data.<br>
<br>
Mark<br>
<blockquote
cite="mid:1458220EF3BF0A44B6606275868BF106AC57AB@nterra-serv3"
type="cite">
<p><font size="2">
<br>
Thanks for your ideas<br>
Thomas</font>
</p>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
rules-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/rules-users">https://lists.jboss.org/mailman/listinfo/rules-users</a>
</pre>
</blockquote>
<br>
</body>
</html>