@SouNayi, good find. @Arjun You should be able to workaround that bug by providing the correct value for that 'find' sql statement through configuration. See an example in this thread that overrides the createtables statement list: http://mail-archives.apache.org/mod_mbox/activemq-users/201108.mbox/%[email protected]%3E
Do a variant that provides an override for findAllDestinationsStatement The correct value is in the diff: http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/store/jdbc/Statements.java?r1=1179999&r2=1179998&pathrev=1179999 On 4 April 2013 09:42, SuoNayi <[email protected]> wrote: > 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. > -- http://redhat.com http://blog.garytully.com
