When we execute a stateless process that exceeds maximum limit: 100. The workflow may be running in
Hi all. We have a new xcp 2.1 installation with the following patches : Content (P09), CTS (P08), DFC (P09), Process engine (P08), the spanish language pack is installed in the repository.
When we execute a stateless process with more than 100 activities the following error ocurs
Activities executed exceeded maximum limit: 100. The workflow may be running in a loop
This is the log
com.documentum.bpm.engine.StatelessEngine] - Unable to obtain activities execution limit from stateless.pe.properties file. Setting default value 100
java.util.MissingResourceException: Can't find bundle for base name statelesspe, locale en_US
at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:1499)
at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1322)
at java.util.ResourceBundle.getBundle(ResourceBundle.java:724)
at com.documentum.bpm.engine.StatelessEngine.initalizeInternal(StatelessEngine.java:60)
at com.documentum.bpm.engine.StatelessEngine.initialize(StatelessEngine.java:52)
at com.documentum.bps.statelessProcess.outbound.runtime.StatelessProcessService.executeServiceOperation(StatelessProcessService.java:97)
Comments
-
Hi,
please check this post it contains already details about this elements/limitation.
stateless process has the limitation of the number of activity that should run.
updating the statelesspe.properties with the entry mentionned in the previous post is necessary if you want to break this limite and this both in JMS & web application ( since stateless process related to UI Action are run in webapp )
i would more recommande spliting your processing to sub processes or using module to achieve loop or calculation activities ( most of the time we use 3 activity to achieve a simple function )
hope this helps
Otman
0 -
Hi Otman, we did the procedure you presscribed:
Modify (or create) the statelesspe.properties file found in <JMS>\DctmServer_MethodServer\deploy\bpm.ear\APP_INF\classes
max.exec.activities.limit=<your number>
and restart the JMS
But the same error shows after we restarted the JMS
0 -
Hi Otman,
I am answering a post of a while ago, but since some people may have the same issue, this may be useful.
You mention that your issue occurs in a STATELESS process.
These processes are run on the xCP application server, not on the JMS.
So please create/edit the statelesspe.properties on the xCP application server to solve this issue.
0
Categories
- All Categories
- 107 Developer Announcements
- 53 Articles
- 106 General Questions
- 142 IM Services
- 43 OpenText Hackathon
- 32 Developer Tools
- 20.6K Analytics
- 4.1K AppWorks
- 8.9K Extended ECM
- 898 Cloud Fax and Notifications
- 76 Digital Asset Management
- 9.3K Documentum
- 29 eDOCS
- 118 Exstream
- 39.8K TeamSite
- 1.7K Web Experience Management