I don't think its recommended to simply move the files in your database. This would bring the journal out of sync. Perhaps it worked in 5.3 but I don't think thats a good way to do.
If you really need to move msgs from one queue to another you should use some external tool. The broker exposes a number of JMX operations which also allows you to move messages to different destinations. So using jconsole you can move messages. Alternatively it is very simple to write a little Camel route that moves all msgs from the DLQ to the messages original destination. Please note that messages on DLQ can have different origins. There is a message header that specifies the original destination name. The Camel route could route messages based on this header. Hope this helps. Torsten Mielke tors...@fusesource.com tmielke.blogspot.com On Nov 13, 2012, at 9:59 AM, Tobb wrote: > Hi, > > We recently updated from AMQ 5.3.0 to AMQ 5.6.0. We are using a database for > storing persistent messages, with journaled mode (in AMQ 5.3.0 it was > JournaledPersistenceAdapter, in 5.6.0 JournaledPersistenceAdapterFactory). > We recently had a problem with 4000 messages ending up in a dead-letter > queue, and because of the number of messages we moved them in the database. > But then, a problem occured: ActiveMQ wouldn't restart, due to some error > with the journal-files (i'm guessing because of a mismatch between the > journal and the database). So, we had to remove the journal files to get AMQ > up and running again. This was not the case with AMQ 5.3.0, we could move > messages in the database without having trouble with journals. > > So, my question is: What is the recommended way of moving a lot of messages > at once when using a journaled persistence adapter with a SQL-database? > > -Tobb > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Mass-moving-messages-tp4659228.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
