| Author |
Message
|
| Sumi |
 Posted: Tue Jun 12, 2012 3:46 am Post subject: Retry flow mechanism |
 |
|
Novice
Joined: 13 May 2012
Posts: 11
|
Hi All,
I want to implement a retry mechanism in MB V8. The main flow is as follows.
Soap input -- > compute node which creates the soap request -- > soap request node --> soap reply node.
Now the scenario is in case the back end webservice is down, an exception is raised. in this case we need to store the request message and post the message again after a certain time interval say one hour.
may be we can have the retry flow to resend the message thrice and then we can send back a fault reply to the front end .
Thanks in advance,
Sumi
 |
|
| Back to top |
|
 |
| kash3338 |
| Posted: Tue Jun 12, 2012 3:51 am Post subject: |
|
|
Shaman
Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India
|
|
| Back to top |
|
|
| marko.pitkanen |
| Posted: Tue Jun 12, 2012 4:09 am Post subject: |
|
|
Chevalier
Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
|
Hi Sumi,
Which transport method you are using with your Soap Input / Output nodes? What kind of transaction (a/synchronic) you are using with requester?
If you are participating in synchronic transaction over http you should perhaps consider to let ultimate requester to do retrying.
--
Marko |
|
| Back to top |
|
|
| Esa |
| Posted: Tue Jun 12, 2012 4:29 am Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| marko.pitkanen wrote: |
If you are participating in synchronic transaction over http you should perhaps consider to let ultimate requester to do retrying.
|
Yes, unless the operations are ONE WAY. |
|
| Back to top |
|
|
| Sumi |
| Posted: Tue Jun 12, 2012 4:33 am Post subject: |
|
|
Novice
Joined: 13 May 2012
Posts: 11
|
@Kash3338.. thanks for the suggestion, i never knew about this earlier, will try exloring this.
@Marko.. right now it is a synch flow. and the transportation used is http. As you said i guess it would be good if the requestor sent the message again.. but i was lookng for other options too. |
|
| Back to top |
|
|
| Sumi |
| Posted: Tue Jun 12, 2012 4:37 am Post subject: |
|
|
Novice
Joined: 13 May 2012
Posts: 11
|
| @esa its a synch flow , we do send back a soap reply or a soap fault. |
|
| Back to top |
|
|
| marko.pitkanen |
| Posted: Tue Jun 12, 2012 4:48 am Post subject: |
|
|
Chevalier
Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
|
Hi Sumi,
With synchronous WS over http you could find your self quite easy from the situation that original requester don't listen the http socket any more if your retry mechanism have long delays. But you can perhaps try to store the key that refers the correct socket with you business data and implement delayed retry inside your flow.
--
Marko |
|
| Back to top |
|
|
| Esa |
| Posted: Tue Jun 12, 2012 5:07 am Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| And, depending on how you select to implement the delay, RequestIdentifier. |
|
| Back to top |
|
|
|
|
