Hey Claus - we can work on a 5.10.2; this bug exists in 5.10.1? Before starting down that route, though, is it possible to clarify the impact of this bug? It sounds like a nuisance from what I read - and could hurt performance in some use-cases. Is that fair?
-- View this message in context: http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-11-0-rc3-tp4690743p4691299.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
