You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@synapse.apache.org by stlecho <st...@gmail.com> on 2008/01/10 12:03:37 UTC
Automatic retry mechanism
Hi,
In the application we are developing, we are contacting external
Webservices.
When these Webservices are - for some reason - not available, we would like
to automatically retry to contact the Webservice after a pre-defined number
of minutes. When the Webservice is at that point in time available, the call
will succeed. If the Webservice is still not available, a second retry
should be issued. This retry mechanism will stop when a pre-defined maximum
number of retries is attained.
Is this type of functionality - out-of-the-box or by custom-build extension
- supported by Apache Synapse ?
Regards, Stefan Lecho.
--
View this message in context: http://www.nabble.com/Automatic-retry-mechanism-tp14731149p14731149.html
Sent from the Synapse - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-user-help@ws.apache.org
Re: Automatic retry mechanism
Posted by ru...@gmail.com.
Hi all,
This is just a wild thought, can't we use a long running task (synapse
startup task) to handle the automatic retrying.
Well, even though for the moment there is no direct link between
mediators and tasks in synapse, we could write a task that lets you
put messages with the retrying endpoint in to a queue associated with
that task and let the task handle the retrying mechanism. Or we could
neglect the tasks and implement this using the synapse timer.
But, we need to provide the connector to the retrying message that we
will have to decide on which will be executed after the message gets
successfully delivered to the retrying endpoint.
Thanks,
Ruwan
On 1/11/08, stlecho <st...@gmail.com> wrote:
>
> Hi Paul,
>
> In another non-ESB based application we have build, we've implemented this
> automatic retry mechanism with a JMS-based approach.
> This application sends XML Messages to a Queue, a Message-Driven Bean picks
> the message up and tries immediately to contact the external webservice. If
> this call fails, specific meta-data - linked to the automatic retry
> mechanism - are added to the original XML message and this message is
> injected again in the Queue.
> With JBoss you can control the delay with which the message will be
> processed by the Message-Driven Bean, so the message will be processed after
> a pre-defined delay. JBoss stores the message in its internally HSQL
> database until it gets treated correctly, i.e. there was no exception during
> the processing phase.
>
> Any suggestions for implementing a similar use case with Synapse ?
>
> Regards, Stefan Lecho.
>
>
> pzfreo wrote:
> >
> > Can I ask how you want to kick this off? I guess a message over a
> > truly asynchronous approach like JMS or WS-Addressing would be ok.
> >
> > We already support timeouts and failure handling, so I think this
> > would be a pretty simple extension. I guess I'm still thinking what we
> > do with the message while we are waiting the n minutes.
> >
> > Its definitely a good use case for Synapse.
> >
> > Paul
> >
> >
> >
> > On Jan 10, 2008 11:03 AM, stlecho <st...@gmail.com> wrote:
> >>
> >> Hi,
> >>
> >> In the application we are developing, we are contacting external
> >> Webservices.
> >>
> >> When these Webservices are - for some reason - not available, we would
> >> like
> >> to automatically retry to contact the Webservice after a pre-defined
> >> number
> >> of minutes. When the Webservice is at that point in time available, the
> >> call
> >> will succeed. If the Webservice is still not available, a second retry
> >> should be issued. This retry mechanism will stop when a pre-defined
> >> maximum
> >> number of retries is attained.
> >>
> >> Is this type of functionality - out-of-the-box or by custom-build
> >> extension
> >> - supported by Apache Synapse ?
> >>
> >> Regards, Stefan Lecho.
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Automatic-retry-mechanism-tp14731149p14731149.html
> >> Sent from the Synapse - User mailing list archive at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: synapse-user-help@ws.apache.org
> >>
> >>
> >
> >
> >
> > --
> > Paul Fremantle
> > Co-Founder and VP of Technical Sales, WSO2
> > OASIS WS-RX TC Co-chair
> >
> > blog: http://pzf.fremantle.org
> > paul@wso2.com
> >
> > "Oxygenating the Web Service Platform", www.wso2.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: synapse-user-help@ws.apache.org
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Automatic-retry-mechanism-tp14731149p14744243.html
> Sent from the Synapse - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: synapse-user-help@ws.apache.org
>
>
--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-user-help@ws.apache.org
Re: Automatic retry mechanism
Posted by stlecho <st...@gmail.com>.
Hi Paul,
In another non-ESB based application we have build, we've implemented this
automatic retry mechanism with a JMS-based approach.
This application sends XML Messages to a Queue, a Message-Driven Bean picks
the message up and tries immediately to contact the external webservice. If
this call fails, specific meta-data - linked to the automatic retry
mechanism - are added to the original XML message and this message is
injected again in the Queue.
With JBoss you can control the delay with which the message will be
processed by the Message-Driven Bean, so the message will be processed after
a pre-defined delay. JBoss stores the message in its internally HSQL
database until it gets treated correctly, i.e. there was no exception during
the processing phase.
Any suggestions for implementing a similar use case with Synapse ?
Regards, Stefan Lecho.
pzfreo wrote:
>
> Can I ask how you want to kick this off? I guess a message over a
> truly asynchronous approach like JMS or WS-Addressing would be ok.
>
> We already support timeouts and failure handling, so I think this
> would be a pretty simple extension. I guess I'm still thinking what we
> do with the message while we are waiting the n minutes.
>
> Its definitely a good use case for Synapse.
>
> Paul
>
>
>
> On Jan 10, 2008 11:03 AM, stlecho <st...@gmail.com> wrote:
>>
>> Hi,
>>
>> In the application we are developing, we are contacting external
>> Webservices.
>>
>> When these Webservices are - for some reason - not available, we would
>> like
>> to automatically retry to contact the Webservice after a pre-defined
>> number
>> of minutes. When the Webservice is at that point in time available, the
>> call
>> will succeed. If the Webservice is still not available, a second retry
>> should be issued. This retry mechanism will stop when a pre-defined
>> maximum
>> number of retries is attained.
>>
>> Is this type of functionality - out-of-the-box or by custom-build
>> extension
>> - supported by Apache Synapse ?
>>
>> Regards, Stefan Lecho.
>> --
>> View this message in context:
>> http://www.nabble.com/Automatic-retry-mechanism-tp14731149p14731149.html
>> Sent from the Synapse - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: synapse-user-help@ws.apache.org
>>
>>
>
>
>
> --
> Paul Fremantle
> Co-Founder and VP of Technical Sales, WSO2
> OASIS WS-RX TC Co-chair
>
> blog: http://pzf.fremantle.org
> paul@wso2.com
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: synapse-user-help@ws.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Automatic-retry-mechanism-tp14731149p14744243.html
Sent from the Synapse - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-user-help@ws.apache.org
Re: Automatic retry mechanism
Posted by Paul Fremantle <pz...@gmail.com>.
Can I ask how you want to kick this off? I guess a message over a
truly asynchronous approach like JMS or WS-Addressing would be ok.
We already support timeouts and failure handling, so I think this
would be a pretty simple extension. I guess I'm still thinking what we
do with the message while we are waiting the n minutes.
Its definitely a good use case for Synapse.
Paul
On Jan 10, 2008 11:03 AM, stlecho <st...@gmail.com> wrote:
>
> Hi,
>
> In the application we are developing, we are contacting external
> Webservices.
>
> When these Webservices are - for some reason - not available, we would like
> to automatically retry to contact the Webservice after a pre-defined number
> of minutes. When the Webservice is at that point in time available, the call
> will succeed. If the Webservice is still not available, a second retry
> should be issued. This retry mechanism will stop when a pre-defined maximum
> number of retries is attained.
>
> Is this type of functionality - out-of-the-box or by custom-build extension
> - supported by Apache Synapse ?
>
> Regards, Stefan Lecho.
> --
> View this message in context: http://www.nabble.com/Automatic-retry-mechanism-tp14731149p14731149.html
> Sent from the Synapse - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: synapse-user-help@ws.apache.org
>
>
--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-user-help@ws.apache.org