You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by ext2 <xu...@tongtech.com> on 2010/10/13 14:59:56 UTC
how about robust-stop and try stop strategy support of camel while stop the application
Hi:
I have post the question. But it seems I doesn't illustrate the
usage clearly and cause some confuse things. So I re-write the use case,
and repost the subject again. I am regret for it :(.
While the manager decide to stop the applications. They often
encounter such situations;
1: Sometimes , system shutdown is urgent, and the application must
be stopped in time. And the user want the application support some robust
strategy to avoid lost messages at this situation;
The camel's graceful-shutdown strategy support the technical
framework to fulfil such situations; But how to achieve the robust purpose,
it's another question. and it's not key-point here; (Actually, it's too hard
to guarantee not to lost any message, even it's impossible sometimes. We
will have a risk to lost the being processed message. So we need another
stop strategy as following).;
2: Sometimes, system shutdown is not urgent. and the manager has
enough time to waiting applications to stop and the manager doesn't want
take the risk of lost message; At such case, the manager require another
stop strategy: just trying to stop in the give time. if time expired, it
doesn't stop the system and just report stopping failed to tell the manager:
application cannot be shutdown now, it's working.
And how does camel support such stop strategy ?
Re: how about robust-stop and try stop strategy support of camel while stop the application
Posted by ext2 <xu...@tongtech.com>.
I see, thanks a lot
============================================================
> Willem Jiang [mailto:willem.jiang@gmail.com]
> 2010年10月14日 14:34
> users@camel.apache.org
>Re: how about robust-stop and try stop strategy support of camel while stop
the application
I don't think current Camel can do the job 2.
But you can easily write a customer ShutdownStrategy which extends the
default one and configure it into Camel.
On 10/13/10 8:59 PM, ext2 wrote:
>
> Hi:
> I have post the question. But it seems I doesn't illustrate the
> usage clearly and cause some confuse things. So I re-write the use case,
> and repost the subject again. I am regret for it :(.
>
> While the manager decide to stop the applications. They often
> encounter such situations;
> 1: Sometimes , system shutdown is urgent, and the application must
> be stopped in time. And the user want the application support some robust
> strategy to avoid lost messages at this situation;
> The camel's graceful-shutdown strategy support the technical
> framework to fulfil such situations; But how to achieve the robust
purpose,
> it's another question. and it's not key-point here; (Actually, it's too
hard
> to guarantee not to lost any message, even it's impossible sometimes. We
> will have a risk to lost the being processed message. So we need another
> stop strategy as following).;
>
> 2: Sometimes, system shutdown is not urgent. and the manager has
> enough time to waiting applications to stop and the manager doesn't want
> take the risk of lost message; At such case, the manager require another
> stop strategy: just trying to stop in the give time. if time expired, it
> doesn't stop the system and just report stopping failed to tell the
manager:
> application cannot be shutdown now, it's working.
> And how does camel support such stop strategy ?
>
>
>
--
Willem
----------------------------------
Open Source Integration: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: http://twitter.com/willemjiang
Re: how about robust-stop and try stop strategy support of camel
while stop the application
Posted by Willem Jiang <wi...@gmail.com>.
I don't think current Camel can do the job 2.
But you can easily write a customer ShutdownStrategy which extends the
default one and configure it into Camel.
On 10/13/10 8:59 PM, ext2 wrote:
>
> Hi:
> I have post the question. But it seems I doesn't illustrate the
> usage clearly and cause some confuse things. So I re-write the use case,
> and repost the subject again. I am regret for it :(.
>
> While the manager decide to stop the applications. They often
> encounter such situations;
> 1: Sometimes , system shutdown is urgent, and the application must
> be stopped in time. And the user want the application support some robust
> strategy to avoid lost messages at this situation;
> The camel's graceful-shutdown strategy support the technical
> framework to fulfil such situations; But how to achieve the robust purpose,
> it's another question. and it's not key-point here; (Actually, it's too hard
> to guarantee not to lost any message, even it's impossible sometimes. We
> will have a risk to lost the being processed message. So we need another
> stop strategy as following).;
>
> 2: Sometimes, system shutdown is not urgent. and the manager has
> enough time to waiting applications to stop and the manager doesn't want
> take the risk of lost message; At such case, the manager require another
> stop strategy: just trying to stop in the give time. if time expired, it
> doesn't stop the system and just report stopping failed to tell the manager:
> application cannot be shutdown now, it's working.
> And how does camel support such stop strategy ?
>
>
>
--
Willem
----------------------------------
Open Source Integration: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: http://twitter.com/willemjiang