Re: [rules-users] rule infinitely loops, appears to be depending on naming on variable

At the moment, @propertyReactive uses a bit mask internally... and I believe that is limited to 64 bits, which corresponds to 64 fields, less than what you have. I'm not 100% sure since I didn't check, but I have the feeling that it may explain what is going on here.. You have something like 160 fields, which is 128+32.. adding or removing one might indeed make a difference! This may indeed be a (known?) bug or limitation of the current impl, Mario Fusco will be able to provide more insight.. You can easily work around the problem, at least for now, by preventing the loop with updatedArBankruptcyChapterPopulated != "No" A side question would be: do you really need all those fields in the same class? Wouldn't it be more reasonable to split it them in multiple beans, rather than a single generic "Facts" class? I'm not familiar with the domain, but the properties seem very hetherogeneous... Also in terms of efficiency and memory consumption, would an average instance of yours have most of those fields populated? Best Davide -- View this message in context: http://drools.46999.n3.nabble.com/rule-infinitely-loops-appears-to-be-dep... Sent from the Drools: User forum mailing list archive at Nabble.com.