activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andres Rangel" <>
Subject RE: Redelivering messages inconsistency
Date Wed, 17 Sep 2008 21:36:41 GMT
I found the problem.
The problem is in resources. 

Does anybody know where can I find a good documentation on how to
configure the activemq.xml file?
I have looked in the documentation but is confusing.

Anyways the changes I made are:

I had in my activemq.xml file the following properties:
                    <policyEntry queue=">" memoryLimit="100mb"/>  // I
had 5mb before, changed it to 100 mb
                    <policyEntry topic=">" memoryLimit="5mb">

            <amqPersistenceAdapter syncOnWrite="false"
directory="${activemq.base}/data" maxFileLength="200 mb"/> //it was 2mb


                    <memoryUsage limit="512 mb"/> // upped to half a gig
                    <storeUsage limit="1 gb" name="foo"/> 
                    <tempUsage limit="100 mb"/>

-----Original Message-----
From: Andres Rangel [] 
Sent: Wednesday, September 17, 2008 3:41 PM
Subject: Redelivering messages inconsistency

Hi We have been working on with ActiveMQ on a custom content based

We first try to use Camel, but since the routes changed very often (the
routing instructions) then we decided to implement it using standard jms
code ,and deploying it in an embedded broker.



The Content Based Router does the following: reads from a channel, and
depending on the message it redelivers it to another channel.


Everything was working fine in my machine, and when we deployed to a
staging server, we encountered some problems.

The problem is in essence the following: the message gets delivered to
the corresponding channel by the content based Router, but our client
applications (the ones listening to these channels) cannot read those
messages, even though we can see the messages in the queues (using the
admin web console).


After much reading, I decided to "clone the message" that is copy the
incoming message in the content router, and send the new message.

And somehow it resolved the problem.


Today, I rolled back the code, to replicate the issue and could not
replicated. Strangely the application worked and the clients were
reading the messages.


I don't know what is happening.


I am really concerned that this problem may occur again in production
and we will not be able to correct it, since we have not identified the
source of the problem.



Is there a problem for ActiveMQ if I redeliver a message? Or should I
always clone it and send it again?








Andres Rangel

Sw Engineer


View raw message