Suspension of Messages during Shutdown
We have messages that are in a queued state for various reasons and when we do a manual shutdown of the instance, they are moved to a Suspended state. I thought I saw in the documentation somewhere a setting to make sure these messages stay in a queued state and not suspend them. Can someone confirm and point me in the correct location for that documentation, as I am trying to ensure that if we do have to manually shutdown a instance, someone doesn't have to remember to go back in and check for suspended messages and resubmit them?
Thanks
Comments
Hi Scott, that doc is here:
Improving Restarts for Productions with Large Queues
That being said - I thought the move from suspended back to the queue was automatic generally, and wouldn't require a manual resubmit?
"By default, when a production is stopped, any asynchronous messages on the ^Ens.Queue global queue are moved to the ^Ens.Suspended queue. When the production is restarted, they are moved back."
set^Ens.Configuration("Queues","KeepInQueues")=1I just ran through several scenarios of testing the change to Ens.Configuration("Queues","KeepInQueues")=1, but when IRIS was restarted the messages were placed back in the Ens.Suspended queue.
Hi Scott, just to double check that this setting is per namespace. If that isn't working, I'd suggest opening a WRC case.
Any updates on this issue @Vic Sun & @Scott Roth? Was it solved when the setting was done in the right namespace?
Thanks,
Marcel
I was never able to get this figured out. It happens because our Business Process sends to a Business Rule that is disabled and started from our cron.
We just make sure to go check for suspended messages after a fail-over.
There is a difference in behaviour for async vs sync messages if I read the documentation. In my case the messages are synchronous, so this should not apply.