« Return to Thread: Upgrade Mule 2.0.3 to 2.1.0 SimpleRetryConnectionStrategy jms

Re: Upgrade Mule 2.0.3 to 2.1.0 SimpleRetryConnectionStrategy jms

by ddossot :: Rate this Message:

Reply to Author | View in Thread

Nick, what about creating a "retry policy community pack" project in MuleForge then?

D.


On Tue, Oct 14, 2008 at 9:43 AM, NiHeitz <niheitz@...> wrote:

I appreciate your time on this.
I thought you should know that much of the work that goes on in Mule and
gets checked in shows up in Google in your mail archives, regardless of
whether it is geared for the Enterprise Edition or the Community Edition.
I've managed to reconstruct the SimpleRetryPolicyFactory (intended for
enterprise) fairly easily from these archives...what is your position to
posting such a solution to this forum?  I will respect your wishes in this
regard.

Nick Heitz


Travis Carlson-2 wrote:
>
> Just to further clarify, the new implementation of Retry Policies is for
> Mule 2.1, so if the previous implementation met your needs, it shouldn't
> have changed from 1.4.x through 2.0.x
>
> Travis
>
> On Mon, 2008-10-13 at 18:12 +0200, Ross Mason wrote:
>> 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
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>
>
>

--
View this message in context: http://www.nabble.com/Upgrade-Mule-2.0.3-to-2.1.0-SimpleRetryConnectionStrategy-jms-tp19902529p19977493.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



 « Return to Thread: Upgrade Mule 2.0.3 to 2.1.0 SimpleRetryConnectionStrategy jms