Although I don't think I've ever seen it happen, it's easy to imagine
stack overflows during bload and bsave. These functions use Java
serialization, which will save a tree of objects recursively, calling
as many as four or five methods at each level of the tree. The tree
for a Jess LHS can be pretty big and pretty "deep" as it is, so it's
not hard to see why stack overflows are a possibility. INcreasing the
stack space is a logical response to this.
On Mar 3, 2011, at 11:32 AM, Santiago Almirón wrote:
Hello,
I'm writting to you because I'm having some strange problems with
jess api. I'm developing a multi agent system with different Jess
engines and I ussually use bsave() and then bload() for save and
load the state of a engine. I use that because there are particular
cases that I need to revert the engine to a previous state.
That worked ok until now. After I changed some simple rules, I added
some new conditions in LHS of the rules, and I started to get stack
overflows in bload and bsave methods.
As workaround, I increase the size of the java stack but I don't
know if I'm doing something wrong.
¿Are there some recomendations to use bload and bsave?
Thank you in advance.
Santiago
---------------------------------------------------------
Ernest Friedman-Hill
Informatics & Decision Sciences, Sandia National Laboratories
PO Box 969, MS 9012, Livermore, CA 94550
http://www.jessrules.com
--------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users [email protected]'
in the BODY of a message to [email protected], NOT to the list
(use your own address!) List problems? Notify [email protected].
--------------------------------------------------------------------
