Serializing any amount of data while other threads might change that data entails the risk of creating an inconsistent snapshot. Mutual exclusion (locking) would be one way, but since there's no progress during this time anyway you might as well stop the session.

If you have the memory, serialize to a byte[] and write this out to secondary storage after restarting.

-W



On 13 July 2012 03:23, chrisLi <shengtao0077@163.com> wrote:
Hi, droolers,

I need to serialize the session as a snapshot at 23:00 pm every day. So I
want to do the serialization work

in a different thread with session execution.

Is it possible? Or is there any risk?

Thank you  very much

--
View this message in context: http://drools.46999.n3.nabble.com/Is-it-possible-to-serialzie-the-stateful-session-without-stoping-executing-rules-tp4018645.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users