ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum IndexWebSphere Message Broker SupportHTTP webservice retry without losing the message order

Post new topicReply to topic Goto page Previous  1, 2
HTTP webservice retry without losing the message order View previous topic :: View next topic
Author Message
zpat
PostPosted: Mon Oct 09, 2017 4:21 am Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5515
Location: UK

Best to check the requirements before using very complex designs.

If there are different endpoints - better to use different queues, or split the messages up in a message flow.

Keeping things simple is always best. If they need to join up answers then that sounds like an aggregation to me.

I have a rule of thumb - if the design is hard to explain - it's a bad design - don't try and code it.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error.
Back to top
View user's profile Send private message
gbaddeley
PostPosted: Mon Oct 09, 2017 4:30 pm Post subject: Reply with quote

Padawan

Joined: 25 Mar 2003
Posts: 1719
Location: Melbourne, Australia

Regardless of possible designs and solutions in IIB / MQ, any requirement for transaction affinity CANNOT rely on simple IIB flow processing and MQ message delivery to provide ordering.

This logic needs to be implemented in the back-end apps and be very robust and tolerant of failures and delays.

We had a recent case where it was discovered that an IIB interface into a back-end web service had an ordering dependency that was not called out in the design. We made a very strong case that IIB / MQ cannot provide ordering, and the app had to accept that, and modify their design.
_________________
Glenn
Back to top
View user's profile Send private message
Display posts from previous:
Post new topicReply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum IndexWebSphere Message Broker SupportHTTP webservice retry without losing the message order
Jump to:



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
Protected by Anti-Spam ACP


Theme by Dustin Baccetti
Powered by phpBB 2001, 2002 phpBB Group

Copyright MQSeries.net. All rights reserved.