TM1 Forum

I can't run my processes coming out of a Sql server, the error I get says "Evaluation stack overflow". Has anybody ever encountered this before. I checked my feeders and that doesn't seem to be the issue.

Hi CD Hodge,
This usually happens because the nesting of feeders blows the feeder stack. A a single cell can only trigger about 250 other feedersbefore the stack blows. So if you have say a day dimension you can only feed forward 250 days from Jan 1st. In this situation you would have a feeder like this

['Today']=> DB( Cube,....Attrs('Day', !Day,'Next')....)

This would normaly break the stack.
What I do is set my next attribute up so that June the 1 st is not populated and the roll forward of the feeder breaks at June 1st and do the same for Dec 31st as well. You then need two feeders for each year

#Fails on June 1st
['Jan 1st']=>DB( Cube,....Attrs('Day', !Day,'Next')....)
#Fails on Dec 31st
['Jun 2nd']=>DB( Cube,....Attrs('Day', !Day,'Next')....)

This should stop the feeder stack from breaking.

IMO though the feeder stack is too small, we should at least be able to feed a whole year in 1 hit
HTH

I have never encountered this error before, and in fact everything was working and then suddenly it wasn't. Would this also happen when I have setup a nesting feeder for months?

Yes it might depending on your version (hint you might want to update your profile ) . In some releases when the stack blows it can stop any further feeders executing in that cube. You can also find different behaviour as to what breaks (if anything) when the server starts versus a rule save.

If you have a month dimension that is month and year with a lot of months in it then setting up a monthly feeder could blow the feeder stack and may affect other potentially unrelated areas of the same cube. If it is just a month dimension with 12 or 13 values then it would be much harder to blow the stack but still possible. Any cell that feeds over 250 cells has the potential to blow the stack.

Cheers,

How nice. Thanks for your help, got everything working again.

cdhodge2002 wrote:I have never encountered this error before, and in fact everything was working and then suddenly it wasn't. Would this also happen when I have setup a nesting feeder for months?

Yes! I wouldn't say this is a common trap, but reasonably common enough. As data input grows over time nested or recursive feeders can break (due to data being where there was none previously.) This can be avoided by designing in breakpoints as Steve suggested.

A practical example of this should really be included in the rules guide, but then so should a lot of things. It seems this is just one of those things you have to learn along the way.

Hi All,

I too now have a stack overflow

I have added another year into our time dimension and have the error messsage of stackoverflow.

Our model is pretty big, so how can I go about understanding which feeder(s) need splitting up like Steve suggested above, when my error message says:

356792 ERROR 2011-05-10 16:45:15.667 TM1.Server Stack overflow evaluating feeders. Starting cell: A01_POL[CLOSING BALANCE,FCST01,Poland Home Credit,Agents No,I_2006_W52]. Feeder: 1

Is this message telling me the reference of the cell that isn't being fed, and I need to manually go and find the feeder?

Does this mean this is the only cell that is overflowing the stack?

Thanks in advance.

Kirk

Hi Kirk,

The first thing to check if this is actually breaking anything, depending on the nature of your model it might or it might not.

The number after the word feeder (in your case 1) is the number of the feeder in the rule file, so helpfully the message does tell you where the issue starts, (I'm pretty sure I'm not imagining this!). The cell reference is the starting cell that is triggering the failure of the feeder stack. Working on a rough stack size of 250 and starting from a number in 2006 W52, your feeder stack word work for 2007, 2008, 2009, 2010, 2011 assuming you are feeding values forward for a weekly dimension. It would start failing around the end of 2011 and onwards into 2012, so it makes sense that you are now seeing issues.

I still think the stack is too small! Shame no was listening in June 2009.

Hope the above makes sense when applied to your model.

Cheers,