Re: [rules-users] Creating selection filter for PlanningEntity with 4 planning variables

On 07-11-13 16:21, maciekpob wrote: A) First, see what happens if you put on the unionMoveSelector cacheType=PHASE (or STEP). By using a cacheType != JIT you guarantee that the same ChangeMove cannot be selected twice. I would expect you to go out of memory in that case. If that's not the case - then see C). B) Next, see what happens if you put the cacheType=PHASE (or STEP) on every changeMove, but not in unionMoveSelector. This probably fixes the problem and might be your favorite way to do things. But I want to know why you're getting the bailout, so do figure that out and reply :) C) Bailout is normally almost impossible to occur. Let me explain bailout. Bailout only applies with filtering for cacheType=JIT, because JIT selectors are neverEnding. Bailout happens if it's has selected (size * 10) moves (so if there are 1 million possible moves, it must have selected 10 million moves) AND not a single one of them was accepted by the filter. Given the fact that it keeps selecting the same move - and that move is not accepted, that might explain this though. So the real question is why does it keep selecting the same move? Is there only 1 move? PS: what version are you using? I remember fixing a bailout related problem in one of the CR's. Make sure you're using 6.0.0.CR5 or higher.