| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ - Queue dedupping? Remove duplicate messages |
« View previous topic :: View next topic » |
| Author |
Message
|
| rattray |
 Posted: Tue Nov 20, 2018 3:53 pm Post subject: MQ - Queue dedupping? Remove duplicate messages |
 |
|
Newbie
Joined: 20 Nov 2018
Posts: 2
|
Do the newer versions of MQ have built in "dedupping" logic?
e.g. if duplicate messages are dropped on a queue can we set some configurable value to dedup the second instance based on some key?
I'm pretty sure the answer is no just wanted to verify my assumption. |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Tue Nov 20, 2018 7:57 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
You are correct - the answer is no.
_________________
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 |
|
|
| gbaddeley |
| Posted: Wed Nov 21, 2018 2:28 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
There are many possible criteria for a "duplicate" message. If MQ had this feature, there would be a lot of options around which MQMD fields, RFH elements and data that would be included. As MQ messages are ephemeral, and queue depths can go up and down unpredictably, there would also need to be a time constraint.
If your application has a design requirement to dedup, the logic needs to be build into the app. Sorry about that.
You could try creating a RFE with IBM.
_________________
Glenn |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Nov 21, 2018 4:10 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Is your app designed to duplicate messages on purpose? Are the duplicates identical as to MQMD, RFH, and app data?
_________________
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 |
|
|
| gbaddeley |
| Posted: Sun Nov 25, 2018 2:48 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
Actually, any MQ consumer app should be tolerant of duplicate and missing messages in a business functional sense. MQ assures delivery of persistent messages, but they may be delayed or arrive on the destination queue out of order, or the source app may not be producing them as expected (the most common scenario).
_________________
Glenn |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Nov 25, 2018 3:55 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| gbaddeley wrote: |
| Actually, any MQ consumer app should be tolerant of duplicate and missing messages in a business functional sense. MQ assures delivery of persistent messages, but they may be delayed or arrive on the destination queue out of order, or the source app may not be producing them as expected (the most common scenario). |
A well-written app should, but I’ve seen few that are.
_________________
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 |
|
|
|
|
|
| |
|
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
|
|
|
|
