Hi, this is a bug and you can take a look at this: https://issues.apache.org/jira/browse/AMQ-3655
When broker restarts it will issue a sql statement to find all existing destinations in the message table in the database, however the message table name is incorrect or gets misspelled, so you can not see them on the web console. Fortunately the messages on these destinations survive and when a producer or consumer is present the destination get recreated on demand. At 2013-04-04 13:42:19,arjun <[email protected]> wrote: >Hi, > >Can you please confirm whether i can go ahead with my proposed solution? It >doesn't look to be a very neat solution, but we have a production release >coming up this weekend, so appreciate if you can confirm that it should not >have any negative impacts. Willing to explore any alternate options as >well(if anything is possible). >From Gary's question above, it looks like this is not expected behavior? > > > >-- >View this message in context: >http://activemq.2283324.n4.nabble.com/AMQ-5-5-0-queues-having-persistent-messages-dropped-on-restart-tp4665430p4665485.html >Sent from the ActiveMQ - User mailing list archive at Nabble.com.
