activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bruce Snyder <>
Subject Re: AMQ persistence not working for me
Date Wed, 17 Mar 2010 21:17:23 GMT
On Wed, Mar 17, 2010 at 2:02 PM, jumbro <> wrote:
> Hello,
> I have been trying to get persistence working and have been humbled by the
> experience.
> Here is my setup:
> * AMQ 5.3
> * Monitoring via AMQ web console deployed in jetty
> * Using Spring.NET 1.2 / Apache.NMS
> * Tried each of the available AMQ persistence schemes (see attached
> activemq.xml)
> * Set both NmsTemplate.Persistent = true and
> Apache.NMS.Message.NMSPersistent = true on the producer
> * My preference is to use  journaledJDBCAdaptor against Sql Server 2008
> Test performed:
> * start AMQ
> * start my message producer (creates dynamic topic by default)
> * observe messages enqueued to topic via web console
> * stop and start AMQ
> Here are the issues I'm having (consider journaledJDBC case):
> 1) I first noticed that nothing appears to be getting written to my journal
> 2) When restarting AMQ, the output tells me (when starting the journal
> persistence adapter): "Journal Recovered: 0 message(s) in transactions
> recovered" activemq.xml
> 3) When AMQ restarts, the topic and messages have been deleted
> I did do some tests (days/weeks ago) where I saw some messages being logged
> to Sql Server. But at no time did I have a successful test of recycling AMQ
> and seeing the existing queue/topic with pending messages populated.
> Live message production/consumption works great for me, both pub/sub and
> request reply. I just can't get persistence working. Please help!

I know that you are using .NET, but have you walked through the Java
examples first? Just to make sure you understand how it should work.
Here is some info about the examples:

The examples are very simple and straightforward. The only change you
will need to make in order to send persistent messages is to use the
following command when sending:

$ ant producer -Ddurable=true

The ProducerTool class will pick up the durable property and mark the
messages as persistent when it sends them. This will allow you to shut
down ActiveMQ, start up ActiveMQ and still see the 2000 messages in
the queue.

perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"

ActiveMQ in Action:

View raw message