activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepak Kumar" <>
Subject Persisting messages across restarts (AMQ 4.1.1 & 4.1.2)
Date Wed, 23 Apr 2008 18:02:37 GMT
<<Hm.. trying to get this sent to the mailing list. Lets see if this works.
Apologies if this becomes a dupe. >>

Hi Folks,
    I'm hoping this is an easy one to answer for some of you.

    Been using AMQ 4.1.1 for a couple of months now, and only just noticed
that messages that are marked as Persistent, aren't being persisted across
AMQ restarts. At a high level, here are the steps I follow:

- Disable all consumers
- Put a few messages on topic
- Verify topic size is non zero using JMX
- Restart AMQ
- Notice topic size is zero again.

    The message producer definitely sets the
javax.jms.DeliveryMode#PERSISTENT flag (we use Spring's JmsTemplate), and
the broker is configured as follows :

<broker useJmx="true" xmlns=""


      <journaledJDBC journalLogFiles="5"



I've also tried several combinations of the following :
- AMQ Versions 4.1.1, 4.1.2 & 5.0.0
- PersistenceAdapters kaha & journaledJDBC for the 4.1.x and
amqPersistenceAdapter for 5.0.0
- Within the journaledJDBC, 2 different data sources, mysql & derby
- Set  persistent="true" on the <broker>

What am I missing? I've spent the better part of today scouring the internet
for leads, and reading through documentation with little success. If someone
could right this ship, I'd really appreciate it.

I guess more specifically, the questions I've been unable to answer:
- Is AMQ capable of preserving messages across restarts?
- Is AMQ capable of preserving messages across restarts using an embedded
derby instance?
- And the golden ticket : does anybody have configuration they can share to
make it so :) ?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message