<div class="gmail_quote">On Thu, Apr 21, 2011 at 1:56 AM, Wolfgang Laun <span dir="ltr"><<a href="mailto:wolfgang.laun@gmail.com">wolfgang.laun@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
It seems to me that an environment is not the best place for an operation that<br>could depend on the session and/or a client's request. It could be used additionally,<br>but not without the direct approach.<br></blockquote>
<div><br>For the record I totally agree.<br><br>Context, in case it helps: I am in the process of migrating off of a heavily used stateless session bean that--right now--creates StatefulKnowledgeSessions and serializes them to the database in between calls. I've enabled equality checking (vs. identity checking) in the knowledge base, but for some reason after about 20 serialization/deserialization cycles the app server runs out of memory.<br>
<br>I am assuming that JBRULES-2048 is in play here; I was hoping that by supplying my own marshalling strategy I could control how the serialization/deserialization happens and avoid the memory leak.<br><br>Best,<br>Laird <br>
</div></div>