to me that fix is a no-brainer really. an obvious fix the lock between live and backup was repeating the log message in an infinite mode. it was supposed to log only once before getting on a waiting forever until the live is dead.
Anyways, it seems you are going to cherry-pick fixes towards 5.10.x... I've tried with the list you provided and I got lots of clashes.. you will need some manual work to apply the selected patches. How did you pick that list? manually looking at the changes? opening a branch at your local fork (before pushing into apache/master) and doing a git log will help identify better what's going there. On Wed, Apr 22, 2015 at 3:01 PM, artnaseef <[email protected]> wrote: > We can apply that fix it you feel strongly about it. The only reason I'm > holding off that specific fix right now is the discussion I started on the > ticket regarding the desired new state of operation. > > I saw your response there - thank you. If we could get Gary to comment, > that would address or eliminate all of my concern. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/HEADSUP-ActiveMQ-5-10-3-release-preparation-tp4695445p4695451.html > Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. -- Clebert Suconic http://community.jboss.org/people/[email protected] http://clebertsuconic.blogspot.com
