Greetings MQ Gurus...
I have a queue which is stacking up with orphan messages that have been returned after the timeout value in the application. I can’t get the application changed to set the MQGets to use expiry. And the application retries after sometime if it didn’t get a response anyway.
I was wondering if there is a way to force a default expiry on messages that don’t have a value set, on an MQ queue/channel level… let me know if there is a way around…
Eventually, the messages buildup to the maxdepth causing the channel to pause (in absence of a DLQ)…
Thanks in advance,
Jay
I have a queue which is stacking up with orphan messages that have been returned after the timeout value in the application. I can’t get the application changed to set the MQGets to use expiry. And the application retries after sometime if it didn’t get a response anyway.
I was wondering if there is a way to force a default expiry on messages that don’t have a value set, on an MQ queue/channel level… let me know if there is a way around…
Eventually, the messages buildup to the maxdepth causing the channel to pause (in absence of a DLQ)…
Thanks in advance,
Jay
