Upgrade Mule 2.0.3 to 2.1.0 SimpleRetryConnectionStrategy jms

[NiHeitz]

Just attempted to upgrade to new Mule 2.1.0.  It seems that there is no longer a SimpleRetryConnection class for failed jms connections using ActiveMQ.  This was present and worked in Mule 2.0.3.  I read the upgrade path document, and it makes no mention of the removal of this strategy...is there a replacement approach?

My connections no longer recover, and my configuration breaks.  Looks like there is a new RetryPolicy framework, but no concrete Implementation classes for actually attempting a retry that has iterations and delays.  Work in progress?  Not available for community edition?

Any help?

[Travis Carlson-2]

You are correct, I have just added the folllowing section to
http://mule.mulesource.org/display/MULE2INTRO/Migrating+Mule+2.0+to+2.1
explaining this.

Retry Policies (ex-Reconnection Strategies)
-------------------------------------------
Due to some fundamental issues with the previous implementation of
Reconnection Strategies, these have now been redesigned and renamed to
"Retry Policies". The API for implementing retry policies is available
in org.mule.api.retry and related classes in org.mule.retry

Mule Enterprise includes common retry policies which can be configured
in your XML (e.g., <retry:simple-policy count="5" frequency="1000"/>)
but Mule Community users will need to implement their own based on
org.mule.retry.policies.AbstractPolicyTemplate

Travis

On Thu, 2008-10-09 at 09:29 -0700, NiHeitz wrote:

> Just attempted to upgrade to new Mule 2.1.0.  It seems that there is no
> longer a SimpleRetryConnection class for failed jms connections using
> ActiveMQ.  This was present and worked in Mule 2.0.3.  I read the upgrade
> path document, and it makes no mention of the removal of this strategy...is
> there a replacement approach?
>
> My connections no longer recover, and my configuration breaks.  Looks like
> there is a new RetryPolicy framework, but no concrete Implementation classes
> for actually attempting a retry that has iterations and delays.  Work in
> progress?  Not available for community edition?
>
> Any help?

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[NiHeitz]

That's a shame.  It seemed like it worked quite well in the snapshot release of Mule 2.0.3.  Will the EE options be rolled back into the Community Edition at some point?

NiHeitz wrote:

Just attempted to upgrade to new Mule 2.1.0.  It seems that there is no longer a SimpleRetryConnection class for failed jms connections using ActiveMQ.  This was present and worked in Mule 2.0.3.  I read the upgrade path document, and it makes no mention of the removal of this strategy...is there a replacement approach?

My connections no longer recover, and my configuration breaks.  Looks like there is a new RetryPolicy framework, but no concrete Implementation classes for actually attempting a retry that has iterations and delays.  Work in progress?  Not available for community edition?

Any help?

[NiHeitz]

I understand. However, it looks to me like retryPolicy won't work (unless the Enterprise codebase is significantly different to the community) as I've just found the following line in JMSConnector:
if (recoverJmsConnections && getRetryPolicyTemplate() instanceof NoRetryPolicyTemplate && connection != null) { ...go on and register exception listener... }
This suggests to me that only instances of NoRetryPolicyTemplate get Exception callbacks when the JMS broker fails during runtime. You can imagine my concern as I tried to implement my own retryPolicy... Luckily it looks like I can extend NoRetryPolicyTemplate, however non-intuitive that might be. Is the above instance check doing something else I should be aware of?
Nick Heitz

Travis Carlson-2 wrote:

You are correct, I have just added the folllowing section to http://mule.mulesource.org/display/MULE2INTRO/Migrating+Mule+2.0+to+2.1 explaining this. Retry Policies (ex-Reconnection Strategies) ------------------------------------------- Due to some fundamental issues with the previous implementation of Reconnection Strategies, these have now been redesigned and renamed to "Retry Policies". The API for implementing retry policies is available in org.mule.api.retry and related classes in org.mule.retry Mule Enterprise includes common retry policies which can be configured in your XML (e.g., ) but Mule Community users will need to implement their own based on org.mule.retry.policies.AbstractPolicyTemplate Travis

[Travis Carlson-2]

Correct again!

That line was wrong, it and the section below it in JMSConnector have
been recently removed.  I suggest you try using the 2.1.1-SNAPSHOT:

http://snapshots.dist.codehaus.org/mule/org/mule/distributions/mule-full/2.1.1-SNAPSHOT/

Travis

On Sun, 2008-10-12 at 05:23 -0700, NiHeitz wrote:

> I understand. However, it looks to me like retryPolicy won't work
> (unless the Enterprise codebase is significantly different to the
> community) as I've just found the following line in JMSConnector:
> if (recoverJmsConnections && getRetryPolicyTemplate() instanceof
> NoRetryPolicyTemplate && connection != null) { ...go on and register
> exception listener... }
> This suggests to me that only instances of NoRetryPolicyTemplate get
> Exception callbacks when the JMS broker fails during runtime. You can
> imagine my concern as I tried to implement my own retryPolicy...
> Luckily it looks like I can extend NoRetryPolicyTemplate, however
> non-intuitive that might be. Is the above instance check doing
> something else I should be aware of?
> Nick Heitz
>         Travis Carlson-2 wrote:
>         You are correct, I have just added the folllowing section to
>         http://mule.mulesource.org/display/MULE2INTRO/Migrating+Mule
>         +2.0+to+2.1 explaining this. Retry Policies (ex-Reconnection
>         Strategies) ------------------------------------------- Due to
>         some fundamental issues with the previous implementation of
>         Reconnection Strategies, these have now been redesigned and
>         renamed to "Retry Policies". The API for implementing retry
>         policies is available in org.mule.api.retry and related
>         classes in org.mule.retry Mule Enterprise includes common
>         retry policies which can be configured in your XML (e.g., )
>         but Mule Community users will need to implement their own
>         based on org.mule.retry.policies.AbstractPolicyTemplate Travis
>
>
> ______________________________________________________________________
> View this message in context: Re: Upgrade Mule 2.0.3 to 2.1.0
> SimpleRetryConnectionStrategy jms
> Sent from the Mule - User mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[rotten]

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.

[Ross Mason-3]

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

[Travis Carlson-2]

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

[NiHeitz]

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

[ddossot]

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