the root cause is the interaction of the journal and https://issues.apache.org/jira/browse/AMQ-3695
On 15 November 2012 11:33, Gary Tully <gary.tu...@gmail.com> wrote: > Please raise a jira issue to track this. it is not a known issue. > If you don't use virtual topics, a workaround is to set > useVirtualTopics=false on the broker element in xml config. > > On 15 November 2012 11:23, Tobb <torbjor...@gmail.com> wrote: >> We have AMQ 5.6.0 set up using a journaledPersistenceAdapter. In the last few >> days we've experienced numerous problems relating to this. It seems that >> when AMQ is shut down, it dumps its state into the journal files, but when >> we try to start the AMQ service again, it fails due to: >> >> >> >> To solve this, we have to remove the journal files from the disk and >> restart. Since this is in a production environment, I'm not really happy >> having to do this, I fear that data will be lost. >> >> We used journaled persistence with AMQ 5.3.0 previously, and never had this >> problem. Is this a known issue? >> >> -Tobb >> >> >> >> -- >> View this message in context: >> http://activemq.2283324.n4.nabble.com/JournaledPersistenceAdapter-error-prone-tp4659388.html >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > > > -- > http://redhat.com > http://blog.garytully.com -- http://redhat.com http://blog.garytully.com
