Description of problem: Startup failure during recovery when persistent JMS messages are used. Workaround: clean the data dir before restart, or use non-per messages.
Arnaud, can you give some details on the nature or the failure?
Here is the error: 2009-mar-02 12:10:25 debug 192.168.224.71:25030(INIT) config change: 192.168.224.71:25030 192.168.224.71:25005 (joined) 2009-mar-02 12:10:25 notice Journal "TplStore": Created 2009-mar-02 12:10:25 debug Journal "TplStore": Journal directory = "/home/asimon/.qpidd2/rhm/tpl/"; Base file name = "tpl" 2009-mar-02 12:10:25 notice Store module initialized; dir=/home/asimon/.qpidd2 2009-mar-02 12:10:25 info > Default files per journal: 8 2009-mar-02 12:10:25 info > Default journal file size: 24 (wpgs) 2009-mar-02 12:10:25 info > Default write cache page size: 32 (Kib) 2009-mar-02 12:10:25 info > Default number of write cache pages: 32 2009-mar-02 12:10:25 info > TPL files per journal: 8 2009-mar-02 12:10:25 info > TPL journal file size: 24 (wpgs) 2009-mar-02 12:10:25 info > TPL write cache page size: 4 (Kib) 2009-mar-02 12:10:25 info > TPL number of write cache pages: 64 2009-mar-02 12:10:25 notice Recovering from cluster, no recovery from local journal 2009-mar-02 12:10:25 debug Exception constructed: Exchange already exists: amq.topic (MessageStoreImpl.cpp:489) 2009-mar-02 12:10:25 debug Journal "TplStore": Destroyed 2009-mar-02 12:10:25 critical Broker start-up failed: Exchange already exists: amq.topic (MessageStoreImpl.cpp:489)
Duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=486991 *** This bug has been marked as a duplicate of bug 486991 ***