I personally have never seen this behavior on the projects where I've used 5.6.0, 5.8.0, and 5.9.1. Obviously those are different versions than the ones you're using, but in the two years I've been monitoring this list I've also never heard of anyone see this in any version. So since you can't pinpoint an action that triggers it, my default assumption is that it's something related to your environment (such as an unintended interaction with a browser plugin) rather than a bug in ActiveMQ.
If you can pinpoint specific steps that reliably reproduce the problem, please post back here and we can try to figure out what's going on. And in the meantime, thankfully the misbehavior is pretty benign and you can safely just ignore those extra destinations. Tim On Jun 22, 2016 7:32 PM, "RuralHunter" <ruralhun...@gmail.com> wrote: > No, they don't come back immediately if I delete them. But they will appear > occasionally when activemq is running in steady status. There is no easy > observed trigger as far as I know such as restart etc. I don't know if it > is > triggered by admin console reloading since we always need to reload the > admin console if we need to check the status of queues. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Queues-with-empty-name-appear-in-web-console-tp4713148p4713266.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
