KB Article #181119
keep processing messages when a user task is down
Problem
-- when an Integrator user task is down, the system throttle is engaged in Interchange and B2Bi stops processing messages. That is the default behavior. It prevent side effects of this failure until the problem is fixed
-- is there a way to change this and force B2Bi to keep trying to process messages even if a user task is stopped ?
Resolution
* open http://<hostname>:6080/ui/core/SystemProperties and set the messaging.keepprocessing.usertaskdown to true
* this setting should be used very cautiously :
- It makes sense in specific situations, for instance if one of the HME3 task (procengine) is stopped but other HME3 tasks are still running (messages will be processed by the tasks that are still running)
- But if the crash of the procengine is caused by a specific message, it will not help even for the HME3, because the message will stop all the HME3 tasks one after the other
- If the user task that is stopped is mandatory for the processing of the messages
(for instance if the HME uses only one procengine that has stopped), it
will not help and it may cause additional problems (messages will be still be
sent from Interchange to Integrator and will be queued in Integrator
queues)