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?
