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

moritzw over 10 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 moritzw over 10 years ago

Thanks for the reply. I realize that this is not best practice. We just have to change it because of the bug we currently have. Fortunately, there are just a few instances affected.

I am trying to figure out why it's not best practice. What kind of impact can have a larger number? I am guessing it's maily because of memory usage issues that arise with this?

Thanks, Moritz
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 moritzw over 10 years ago

Thanks for the reply. I realize that this is not best practice. We just have to change it because of the bug we currently have. Fortunately, there are just a few instances affected.

I am trying to figure out why it's not best practice. What kind of impact can have a larger number? I am guessing it's maily because of memory usage issues that arise with this?

Thanks, Moritz
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data