<HTML><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18975"></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>Alright. So do I have to worry about contamination between rule flows.</DIV>
<DIV> </DIV>
<DIV>Consider the following scenario:</DIV>
<DIV> </DIV>
<DIV>1) Instantiate Fact Model A with property A = 10.</DIV>
<DIV>2) Insert Fact Model A into Working Memory</DIV>
<DIV>3) Start Process A.</DIV>
<DIV>4) Instantiate second instance of Fact Model A with property A = 20.</DIV>
<DIV>5) Start Process A again.</DIV>
<DIV><BR>So are there now two separate instances of Fact Model A in working memory or is there still only one instance and property A has been updated to 20? Will process B find the correct value (20)? Is it thread safe? Will unused fact objects hang around forever?</DIV>
<DIV> </DIV>
<DIV>Sorry if I'm being a little thick about this. Maybe I'm worrying about nothing.</DIV>
<DIV> </DIV>
<DIV>Thanks for your response.</DIV>
<DIV> </DIV>
<DIV><BR>>>> JeffMax <jeffmax@gmail.com> 2/18/2011 11:31 AM >>><BR><BR>My experience has been (and I believe the expected behavior of stateful<BR>sessions) is that the state of your working memory will not be cleaned up<BR>between flow executions. If,for example, one flow execution inserts a new<BR>fact into working memory, then a subsequent flow execution would see that<BR>fact in working memory.<BR><BR>For my requirements, which was to use Drools-Server as a stateless, request<BR>- response server, with no shared state between requests, it was necessary<BR>to use a stateless session.<BR><BR>- Jeff<BR>-- <BR>View this message in context: <A href="http://drools-java-rules-engine.46999.n3.nabble.com/RuleFlow-only-calling-first-RuleFlowGroup-when-called-through-drools-server-tp2514244p2527353.html">http://drools-java-rules-engine.46999.n3.nabble.com/RuleFlow-only-calling-first-RuleFlowGroup-when-called-through-drools-server-tp2514244p2527353.html</A><BR>Sent from the Drools - User mailing list archive at Nabble.com.<BR>_______________________________________________<BR>rules-users mailing list<BR>rules-users@lists.jboss.org<BR><A href="https://lists.jboss.org/mailman/listinfo/rules-users">https://lists.jboss.org/mailman/listinfo/rules-users</A><BR></DIV><html>
<body>
<p class=MsoPlainText>-------------------------</p>
<p class=MsoPlainText>Statement of Confidentiality</p>
<p class=MsoPlainText>This message (including attachments) may contain
confidential or privileged information intended for a specific individual or
organization. If you have received this communication in error, please notify
the sender immediately. If you are not the intended recipient, you are not
authorized to use, disclose, distribute, copy, print or rely on this email, and
should promptly delete this email from your entire computer system.</p>
<p class=MsoPlainText>-------------------------</p>
</body>
</html>
</BODY></HTML>