As I replied in the jira thread for AMQ-6203, I will backport this for the 5.13.3 release but I will turn it off by default to prevent inadvertent issues. The flag will be configurable to enable in case someone wants to test it in their setup.
On Fri, Apr 8, 2016 at 11:39 AM, artnaseef <[email protected]> wrote: > Yeah, AMQ-6203 should be a big win for a major headache, if the fix > eliminates the problem. > > Please include it in the 5.13.3 release at the very least. Probably a new > release of 5.12.x too, unless 5.14.0 comes out in the next couple of weeks. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-5-13-3-and-5-14-0-release-schedule-tp4710502p4710529.html > Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. >
