Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
7 replies
Subscribers
10 subscribers
Views
7278 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Administration
Activity Chaining Issue
jayashrib223
over 8 years ago
Hi,
We have following in custom.properties:
server.conf.exec.CHAINED_EXECUTION_NODE_LIMIT=100
Still in db_PX*.log file we are seeing error for one process:
[Activity Chaining] Could not chain to attended activity. Limit of 50 unattended nodes executed was reached.
Attached log file. Any hep?
OriginalPostID-230151
db_PX001_2016-05-13_0242.log
Discussion posts and replies are publicly visible
Parents
0
Roshan Rokade
over 6 years ago
@Jayshrib: have u faced any issue on the system or any adverse impact on the system after increasing the limit to 100?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Roshan Rokade
over 6 years ago
@Jayshrib: have u faced any issue on the system or any adverse impact on the system after increasing the limit to 100?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
0
ericg329
Certified Lead Developer
over 6 years ago
in reply to
Roshan Rokade
Configuring the activity chaining limit to 100 will not in and of itself cause performance issues on your system. Understanding the performance impact is dependent of what is chained, how the user interacts with that process flow, and what kind of load the process will put on the system across active processes.
The reason raising the limit is not recommended is that a chain that large is a red flag that there could be problems and the design should be reviewed for optimization. I would argue it is pretty rare that a chain that large doesn't have a negative impact on system performance or user experience.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel