Activities executed exceeded maximum limit: 100. The workflow may be running in a loop

Good Morning everyone

I have a stateless process and when it runs in the application, I get the following error: "Activities executed exceeded maximum limit: 100. The workflow may be running in a loop". I know I've seen something about changing properties before to allow it to exceed that amount (statelesspe.properties) but I am not sure where that file is located or if I have to create it, where does it need to go? I've heard in JMS and also in application server. If it is in the application server, is there a specific folder it belongs in?

I am currently running Documentum XCP 16.7.

Thank you

Find more posts tagged with

Comments

DCTM_Guru

Instead of trying to fix the problem, why is your stateless process getting called over 100 times (ie what does it actually do)?

Dustin76

This is a process that was in place before I was on the system. The process loops through a spreadsheet row by row to get information to create new folders as it loops through, it runs a check to see if the folder exists already. If it does, it iterates to the next row. Then it creates the folders. This is done by calling a different stateless process. We never know how many rows will be in the spreadsheet but the user always gets the error. I can go into designer and run the process from there and it will run all the way through but that gets to be a hassle. I'm not trying to recreate the process at this time because I have other fires I have to put out before I can do that so I just need to fix this problem for now and I've heard doing the statelesspe.properties will fix the problem.

DCTM_Guru

I'm not familiar with properties, but we got around this issue by running business logic in server method instead of using stateless process. Obviously, this requires recoding and as you stated, you are not trying to refactor the code. You should submit ticket to OpenText support. They should be able to provide technical details if you maintenance contract is active.

Bozon

This is just a configurable limit and it is well documented:

You need to create a statelesspe.properties files on the customconfig folder for your App Server (Tomcat and JBoss for the JMS)

on that file configure the maximum amount of activities by setting:

max.exec.activities.limit=80000 (I have this limit and my system works fine).

You need to consider your Java heap memory configuration and maximum stack deep to support big activity numbers.

Hope this helps.

Regards!