| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Reset MQ Channel |
« View previous topic :: View next topic » |
| Author |
Message
|
| avakado |
 Posted: Mon May 04, 2009 8:36 am Post subject: |
 |
|
Newbie
Joined: 19 Mar 2009
Posts: 5
|
"Channel sequence numbers are MQ's way of assuring guaranteed delivery - the sender channel deletes the messages from the xmitq only after it has got the assurance from the receiver channel that it has received those messages."
If the receiving MCA puts the message to the DLQ for whatever reason, the transacition is successful from the sender MCA's perspective?
Is there a way that the remote sending application can be notified when a message goes to the DLQ?
We have an application where order is important, so if messages go to the DLQ downstream, order might be lost.
avakado |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon May 04, 2009 8:45 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| avakado wrote: |
| If the receiving MCA puts the message to the DLQ for whatever reason, the transacition is successful from the sender MCA's perspective? |
Yes
| avakado wrote: |
| Is there a way that the remote sending application can be notified when a message goes to the DLQ? |
No
| avakado wrote: |
| We have an application where order is important, so if messages go to the DLQ downstream, order might be lost. |
This is called message affinity, and has been discussed many times in this forum. It's a very bad idea (for reasons previously discussed) and you should redesign to remove it.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon May 04, 2009 8:49 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.
|
If order of retrieval is important, look at MessageGroups in the APR and APG
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon May 04, 2009 9:04 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| avakado wrote: |
| Is there a way that the remote sending application can be notified when a message goes to the DLQ? |
Yes.
Have the sending app set the MQRO_EXCEPTION and MQRO_DEAD_LETTER_Q options. If you get an Exception Report Message, you know the message went to the DLQ. If you do not get an exception report, well, it probably worked. But maybe the report message is having a problem coming back.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| darthvieder |
| Posted: Sat Jul 11, 2009 3:43 am Post subject: |
|
|
Newbie
Joined: 11 Jul 2009
Posts: 1
|
| interesting.. im going to check this one out.. thanks a lot |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sat Jul 11, 2009 6:19 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| Is there a way that the remote sending application can be notified when a message goes to the DLQ? |
A broader view of this issue:
Applications should be written to be sensitive to loss or duplication of messages (by applications or other infrastructure).
A requesting app should know that it sent request 1,2,3; but only received replies 1 and 3, and re-send request 2.
Likewise, the replying app should know that it recieved requests 10 and 12; but did not receive request 11.
Appropriate business logic would dictate what the apps should do in either case. This can eliminate (transaction) issues like msgs going to dlq.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| aberde |
| Posted: Wed Oct 28, 2015 8:06 pm Post subject: which value need to set RESETSEQ |
|
|
Newbie
Joined: 06 Oct 2015
Posts: 7
|
| Which recommended value for RESETSEQ |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Oct 28, 2015 8:27 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.
|
This is a 6 year old post.
And, you've posted this elsewhere.
RESETSEQ ia a parameter of the RESET CHANNEL command.
Have you looked at the RESET CHANNEL command http://www-01.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.ref.adm.doc/q086510_.htm
The command is used when one of the end of the channel tries to start, but the SEQWRAP values are different - which prevents the channel from starting.
If this is the issue you are facing, you need to figure out how/why the two channel ends have different values.
The command can be issued from the sender end, and it will reset both ends of the channel to whatever value you choose. 1 is a good value.
If you issue the command from the receiver end, use the value from the sender end.
What version/release/fixpack of MQ are you running?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
