| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| HTTP and assured, once-only delivery via MB flow |
« View previous topic :: View next topic » |
| Author |
Message
|
| sunny_30 |
 Posted: Fri Sep 27, 2013 6:16 pm Post subject: HTTP and assured, once-only delivery via MB flow |
 |
|
Master
Joined: 03 Oct 2005
Posts: 258
|
I have a Broker message flow that takes a SOAPinput, and later persists to the MQ layer. If the SOAPreply post back to the web-client has failed, the flow is designed to discard the MQ message expecting the web-client to retry the request again.
My question now is to know IF there will be a scenario where the web-client actually received the SOAP response but the flow failed due to a bad return code for the HTTP post.
Also- in general, there is a theory that HTTP cannot be assured and cannot be guaranteed for once-only delivery as MQserver connection does.
Can one please lay out a message-flow SOAPreq-response scenario (flow acting as both a http client or as a webserver) that the message might get lost or duplicated please |
|
| Back to top |
|
 |
| Simbu |
| Posted: Fri Sep 27, 2013 10:32 pm Post subject: Re: HTTP and assured, once-only delivery via MB flow |
|
|
Master
Joined: 17 Jun 2011
Posts: 289
Location: Tamil Nadu, India
|
| sunny_30 wrote: |
Also- in general, there is a theory that HTTP cannot be assured and cannot be guaranteed for once-only delivery as MQserver connection does.
|
| Quote: |
WebSphere® Message Broker supports WS-RM (Web Services Reliable Messaging), which allows two systems to reliably exchange messages with each other.
Web Services Reliable Messaging (WS-RM) is an OASIS standard that allows two systems to reliably exchange SOAP messages with each other. The purpose of WS-RM is to ensure delivery of messages in situations such as the destination endpoint being temporarily unavailable (for example, in the case of a server restart) or the message path crossing multiple transport connections, any of which might fail (for example, across a firewall). WS-RM offers greater reliability when using HTTP transport, but has a performance impact.
WS-RM is applicable only to HTTP transport. If you configure WS-RM on a message flow that uses JMS transport, the WS-RM settings are not used when the flow is deployed.
Systems that implement WS-RM retransmit messages that have not been successfully delivered and acknowledged, and prevent duplicate messages from being delivered to the application destination. WS-RM is a web services protocol and can be used with WS-Security and WS-Addressing. |
|
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Mon Sep 30, 2013 3:29 am Post subject: Re: HTTP and assured, once-only delivery via MB flow |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| sunny_30 wrote: |
| My question now is to know IF there will be a scenario where the web-client actually received the SOAP response but the flow failed due to a bad return code for the HTTP post. |
First : You need to track these payloads with a database. You need to be keeping up with payload identifiers, ReplyIds and return codes in your database. There is no mechanism in-built to track this sort of resiliency since the developer is assumed to be intelligent enough to design proper logic.
Second : if you post a payload via any protocol to any downstream provider, and you get an error back, how would you know whether or not the payload successfully or partially processed ? There is no way to know what any downstream provider will do, unless you also wrote the downstream.
C : If you wrote a payload out on an index card and handed it to your buddy for processing, and your buddy handed it back to you with the statement that he could not complete the processing (because he needed to use the C.R.) , what action would you take regardless of your automation state ?
Fourth : This is a use-case for two-phase commit. If its that important to you to know if the downstream was really successful, you need two calls, one to send the data, with a response that the data was received and the other to commit the data.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| 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
|
|
|
|
