I have one process where a work-step loops until a condition is met. After a while it gets suspended with the following error:
Loopcounter for workstep <Processing Message> for PI <MBAInterfaceHeartBeat#3744> has already reached maximum limit of <500>.
I found an article where it mention about the 'activationcount' property. Do you know where it can be set ?
I found a reference in a propoerty setup file. This property seems to be settable from OEBP Portal, but I was not able to find it in OEBP Portal.
Is there is a way to reset this counter when the work-step is activated ?
My flow is designed to run forever.
I loop through one activity for several times, when a condition is met, I move to other activity (when it send an email) and come back later to looping into the first activity again to loop again.
In my tests the activity is looping less than 20 times after each activation. I guess that the looping counter is not reset and it is continuing to count up from where he was left.
I tried the following: I have this setting in Loop: "Loop by ProcessMessageLoopCtr while (!ProcessedAll)". Even i reset the ProcessMessageLoopCtr on activation of the activity i still get the error.
Flag this post as spam/abuse.
My process is suppose to run forever therefore any limit will be reached someday. I prefer to skip validation somehow..
What I see it didn't work is setting the bpserver.ws.max.activationcount=-1 and having the ProcessType as BusinessProcess. Maybe it works if I change it to SystemProcess. I don't know what other implication this change has.
Please refer to OpenEdge® Getting Started: Developing BPM Applications with Developer Studio guide.
Using Advanced tab of Activity workstep properties section.
The Activation Limit checkbox is only available for a system process, as defined in
ProcessType attribute in process properties (see Setting process properties on page 119).
Select this checkbox and enter a value (greater than 0), which sets a maximum limit that this
workstep is executed in loop for a process instance at runtime. To execute the workstep loop
indefinitely, specify the value as -1. If no value is specified, the value of the
bpserver.ws.max.activationcount parameter in the
OEBPS_Home\conf\bpserver.conf file is considered as the maximum limit.
it works with bizlogic.ws.max.activationcount=-1.
We need to explicitly reset/initialize the counter value by using pre/post scripts of an Activity 2. So that when it went to Acitivty1 for looping again, the counter value will start with initial value.
I tried this: on activity completion I reset the counter I defined: ProcessMessageLoopCtr (see my post above). But it didn't solves the problem. The limitation was based on some internal counter which I don't know how to set.