You also need to give us some indication of what your rules look like. Are you
using just patterns, what conditional elements are you using, are you using any
temporal operators, scheduling, tms?
Mark
On 24 Feb 2013, at 06:12, Wolfgang Laun wrote:
> On 24/02/2013, Julian Klein wrote:
>> Ok, t
On 24/02/2013, Julian Klein wrote:
> Ok, thanks. Here's what I have so far:
>
> 1) I am not retracting facts or setting expiration. This is by design
> since I am doing the next item. Do I need to retract globals?
Be careful with globals when you run alike sessions in parallel - the
object(s)
On 24 Feb 2013, at 04:11, Julian Klein wrote:
> Ok, thanks. Here's what I have so far:
>
> 1) I am not retracting facts or setting expiration. This is by design since
> I am doing the next item. Do I need to retract globals?
> 2) I have disposed the session when I ran with a StatefulSession
Ok, thanks. Here's what I have so far:
1) I am not retracting facts or setting expiration. This is by design
since I am doing the next item. Do I need to retract globals?
2) I have disposed the session when I ran with a StatefulSession. I
understood this means I do not need to retract facts.
Take a look at...
org.drools.guvnor.server.security.DemoAuthenticator
Implement a class similar to that and configure that in your beans.xml.
Make the class available in the classpath, thats it.
--
View this message in context:
http://drools.46999.n3.nabble.com/Drools-Guvnor-User-authentication
This is great. It sounds like I have to go back to the drawing board. It
may take a while to work through this list. I'll circle back with outcomes.
Thank you.
___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/li
Typical issues are:
1) Not retracting facts, or setting expiration.
2) Not disposing sessions.
3) Poor discrimination networks that produce too many cross products - put the
strongest descriptors first.
4) Making sure you use constraints that exploit indexing (this makes a huge
difference for per
Although I did see a drop in initial memory usage, things went south again
as the run continued past the 2-4 hour mark. I have poured over my source
several times and am starting to loose faith that Drools can provide
anything other than a single threaded rules engine. Although the engine
itself
