All file based loggers can split their content into multiple files when the
number of recorded events surpasses a given threshold.
It should be quite simple to modify this to be able to pause logging and
resume to a new file when unpaused.
sent on the move
On 18 Dec 2011 18:02, "Mark Proctor" <mproctor(a)codehaus.org> wrote:
I don't believe that is currently possible.
Would make a good project for you to work on. Maybe you should add a
start() and stop() method to the logger. However also make sure that the
resulting fragmented log can be read and used - you may find that it's
effectively corrupted, due to missing references, if you only dump part
of it.
Mark
On 16/12/2011 15:29, jkrupka wrote:
> Am I totally missing something or is there not a way to stop logging of a
> stateful ks once you start doing so via the WorkingMemoryFileLogger (at
> least in Drools 5.2)?
>
> The Event Listeners that get registered when the file logger get created
> don't seem to ever be unregistered, and calling classes don't even have
the
> visibility into the internals of the file logger in order to do so
> themselves.
>
> The use case for this is if you have a long running stateful session and
you
> want to turn on logging just for a short period of time to collect some
> information, then turn logging off again. The only way I know of doing
this
> currently is to reload the whole session.
>
> --
> View this message in context:
http://drools.46999.n3.nabble.com/WorkingMemoryFileLogger-question-tp3591...
> Sent from the Drools: User forum mailing list archive at
Nabble.com.
> _______________________________________________
> rules-users mailing list
> rules-users(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/rules-users
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users