On 27 September 2011 17:25, Hari Kishan
<HariKishan.Tammana(a)pass-consulting.com> wrote:
After Changing to a single Collect ... The Issue is still
reoccurring.
Another alternative is to use an accumulate to compose the List by
init - action - reverse - result. Perhaps this isn't as vulnerable as
collect appears to be.
-W
*But some Observations *:-
1) Every thing works fine till some time . Suddenly the first time exception
comes ,that is it always the same exception keeps popping . The rules
weren't executed i hope may be the Context is lost or something .
(Note :- The above observation is irrespective of the change which i have
done now)
2) when there are 2 Collects , the Exception seem to arrive much earlier
that is (i.e 5-6 mins after the server session started), but after changing
to single Collect the Exception arrived after a long time ( i.e 15 mins
after the server session started) ...... May be this is one time
observation, just want to give you some information which may help you
suggest me something.
3) The lesser the number of conditions the greater the stability of the
application. Drools I think is used for more complex scenarios of the real
world. Our application should not overload the complexity i guess.
--
View this message in context:
http://drools.46999.n3.nabble.com/Getting-Exception-while-running-rules-c...
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