Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

System CRRBF0856I: Inline recursion from step ...

I am getting this Message when I try to execute a project in Build Forge 7.1.3 setup this way:

Project contains 10 threaded steps to execute the same library on 10 separate servers.

Command section for each step is .sleep 0

We have routinely run this type of job in previous versions with no problems.

0 votes



3 answers

Permanent link
I am getting this Message when I try to execute a project in Build Forge 7.1.3 setup this way:

Project contains 10 threaded steps to execute the same library on 10 separate servers.

Command section for each step is .sleep 0

We have routinely run this type of job in previous versions with no problems.


The first part of your message matches a situation when the max inline depth is being exceeded. The default max inline depth is 32. You can check or change what your value is set to by navigating to Administration -> System and filtering for 'Max Inline Depth'.

Brent Ulbricht
RTC Build Lead

0 votes


Permanent link
I am getting this Message when I try to execute a project in Build Forge 7.1.3 setup this way:

Project contains 10 threaded steps to execute the same library on 10 separate servers.

Command section for each step is .sleep 0

We have routinely run this type of job in previous versions with no problems.


The first part of your message matches a situation when the max inline depth is being exceeded. The default max inline depth is 32. You can check or change what your value is set to by navigating to Administration -> System and filtering for 'Max Inline Depth'.

I increased the value for "Max Inline Depth". Then I started to run the above job but looked at the "Job Steps" tab before clicking execute. Each step has a line with under the step name. I then un-threaded the steps making the job 10 separate steps, started the job and looked at the "Job Steps" tab. The Recursion Error message is still there. The library I am trying to execute for each step has 3 pretty basic commands; delete an existing backup if it exists; rename the existing file; move in a new copy of the file.

Brent Ulbricht
RTC Build Lead

0 votes


Permanent link
I am getting this Message when I try to execute a project in Build Forge 7.1.3 setup this way:

Project contains 10 threaded steps to execute the same library on 10 separate servers.

Command section for each step is .sleep 0

We have routinely run this type of job in previous versions with no problems.


The first part of your message matches a situation when the max inline depth is being exceeded. The default max inline depth is 32. You can check or change what your value is set to by navigating to Administration -> System and filtering for 'Max Inline Depth'.

I increased the value for "Max Inline Depth". Then I started to run the above job but looked at the "Job Steps" tab before clicking execute. Each step has a line with under the step name. I then un-threaded the steps making the job 10 separate steps, started the job and looked at the "Job Steps" tab. The Recursion Error message is still there. The library I am trying to execute for each step has 3 pretty basic commands; delete an existing backup if it exists; rename the existing file; move in a new copy of the file.

Brent Ulbricht
RTC Build Lead

The 'Recursion Error: Loop detected' looks like it's emitted when the environment has recursion. Any chance you've got an environment in your project that has includes?

Brent Ulbricht
RTC Build Lead

0 votes

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Sep 15 '11, 10:41 a.m.

Question was seen: 5,554 times

Last updated: Sep 15 '11, 10:41 a.m.

Confirmation Cancel Confirm