Unfortunately reconnection strategies really didn't work well for many
scenarios in Mule 1.x and were not addressed until the most recent
release Mule 2.1 hence they were still broken in 2.0. It sounds like
you've been running just fine in production with your use-case, but
many scenarios were not catered for or didn't work as expected.
The API for the new retry policies is in Mule 2.1 is in the community
edition, but you'll have to write your own retry policies based on you
applications needs.
Cheers,
Ross
On 13 Oct 2008, at 15:57, rotten wrote:
>
> So if I'm understanding this thread, there is NO community release
> where JMS
> retry/reconnection strategies work.
>
> Mule 1.4.3 and 1.4.4 they were broken.
> Mule 2.0.1, and 2.0.2 they were broken.
>
> To get them to work you have to use a snapshot; either the 2.0.3
> snapshot,
> or the new 2.1.1 snapshot.
>
> FWIW, if true, this is a major setback for our implementation of
> Mule in a
> production environment.
> --
> View this message in context:
http://www.nabble.com/Upgrade-Mule-2.0.3-to-2.1.0-SimpleRetryConnectionStrategy-jms-tp19902529p19955435.html> Sent from the Mule - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>
http://xircles.codehaus.org/manage_email>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
