This might be a silly question but i’ll ask it anyways :)
When an Application Message fails within the ‘NOTIFICATION’ queue how do you stop all other jobs waiting until the failed job is cleared? Using Apps 8 by the way.
I see that other Queues work differently, as in keep processing even thought failed messages exist,
In Setup IFS Connect window in IEE, check whether EXECUTE_IN_ORDER check box is checked for NOTIFICATIONS queue.
You can also compare with the configuration of other queues to see what’s different in NOTIFICATIONS queue. For instance, MAX_PROCESSES parameter could be set to a value higher than 1, which would allow more than 1 message to be processed in parallel, given that EXECUTE_IN_ORDER is unchecked.
In Setup IFS Connect window in IEE, check whether EXECUTE_IN_ORDER check box is checked for NOTIFICATIONS queue.
You can also compare with the configuration of other queues to see what’s different in NOTIFICATIONS queue. For instance, MAX_PROCESSES parameter could be set to a value higher than 1, which would allow more than 1 message to be processed in parallel, given that EXECUTE_IN_ORDER is unchecked.
Application Message Queues are developed in order to execute the jobs parallelly in different queues by the processor. If we consider one Queue, there also we can execute the more than one job parallelly by selecting a MAX_PROCESSES parameter in Setup IFS Connect window to more than 1.
If you select 3 in MAX_PROCESSES for NOTIFICATIONS queue, then within a queue 3 jobs can be executed simultaneously. So even 1 job got failed, other 2 jobs will be executing and will pick other waiting jobs once the current job finish.
But make sure the parameter job_queue_processes in database should be equal to the processes defined for all the Queues.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.