Hi, due to a bug we have in an application one of our tasks is increa

moritzw over 11 years ago

Hi,

due to a bug we have in an application one of our tasks is increasing by one every day. Because of that the process will run into an error once the MAX_NODE_INSTANCE property is reached. The processes can in theory run for many years. Our workaround for this is to set the property to infinity in custom.properties:
server.conf.processcommon.MAX_NODE_INSTANCES=2147483647

Anyone aware of any risks we're taking with this? There are currently only about 6-7 instances that have the problem. We've adresses the bug in a current hotfix, so there will be no future processes with that problem.

TIA, Moritz...

Discussion posts and replies are publicly visible

Parents

0 Myles Weber
Appian Employee
over 11 years ago

From what I recall, there are 2 main reasons for this setting.
a) It is to help avoid poor designs as there are better performing alternative ways
b) It avoids unintentional mistakes of run-away processes
There could be performance implications, but without testing that pattern, I couldn't say for sure.
If it is just once a day for many years, I'd suggest using a lower value than near infinity as you still get some of the above benefits.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Myles Weber
Appian Employee
over 11 years ago

From what I recall, there are 2 main reasons for this setting.
a) It is to help avoid poor designs as there are better performing alternative ways
b) It avoids unintentional mistakes of run-away processes
There could be performance implications, but without testing that pattern, I couldn't say for sure.
If it is just once a day for many years, I'd suggest using a lower value than near infinity as you still get some of the above benefits.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data