| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| IBM MQ classes for .NET version 9.3.2 backout queue handling |
« View previous topic :: View next topic » |
| Author |
Message
|
| michel123 |
 Posted: Wed May 10, 2023 5:08 am Post subject: IBM MQ classes for .NET version 9.3.2 backout queue handling |
 |
|
Newbie
Joined: 24 Oct 2022
Posts: 4
|
Using https://www.nuget.org/packages/IBMMQDotnetClient/9.3.2 in a .NET 6 application, I am seeing different behavior regarding backout handling:
- When running against an MQ 9.3.0.0r3 server, messages get moved to the backout queue whenever the BackoutCount property for a message reaches the configured BOTHRESH for that particular queue.
- When running against an MQ 7.5 server, the message stays on the queue when the BackoutCount property for a message reaches the configured BOTHRESH for that particular queue.
I am aware that MQ 7.5 is end of support, however the my customer is using this version. |
|
| Back to top |
|
 |
| hughson |
| Posted: Wed May 10, 2023 3:19 pm Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
Given that all the code for checking the MQMD.BackoutCount and inquiring the attributes on the queue to know where to send messages that exceed the threshold is all in the DotNet client, and not in the queue manager, if you are using the same DotNet code at the client side and the only difference is the queue manager, I suspect that there might be a configuration difference between the two queue managers.
On the queue in question, check that the BOQNAME and BOTHRESH attributes are set correctly.
| Code: |
| DISPLAY QLOCAL(app-q-name) BOQNAME BOTHRESH |
Check your queue manager error logs to see if there were any failures to MQINQ the queue to discover these two attributes on the queue - I am not familiar enough with the DotNet client to know whether or not it would be silent if this happened or whether it would report it as an exception.
Check your queue manager error logs to see if there were any failures to MQOPEN the BOQNAME for +put, same as above.
You are correct that MQ V7.5 is out of support. Perhaps this incident will show your customer the benefits of having support!
Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
