activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Johannes Pieringer (JIRA)" <>
Subject [jira] [Updated] (AMQ-5489) JMSExpiration not working correctly with LevelDB
Date Mon, 15 Dec 2014 09:17:14 GMT


Johannes Pieringer updated AMQ-5489:
    Attachment: JConsole_-_Retry.png

Statistics after 100 messages are sent and expired

> JMSExpiration not working correctly with LevelDB
> ------------------------------------------------
>                 Key: AMQ-5489
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: activemq-leveldb-store
>    Affects Versions: 5.10.0
>         Environment: Solaris and MacOS X, Java 1.6, Camel 2.14 is used for sending messages
to the AMQ.
>            Reporter: Johannes Pieringer
>         Attachments: JConsole_-_ActiveMQ.png, JConsole_-_Retry.png
> I'd like to create a setup where messages with an JMSExpiration header expire in a queue
named "Retry" and are then moved to the "ActiveMQ.DLQ". The messages should then be consumed
from the ActiveMQ.DLQ. As a specialty, the messages are 5MB large.
> The messages do expire in "Retry" and are moved to the "ActiveMQ.DLQ". When the expire
however, I instantly see twice the number of expired messages on the "ActiveMQ.DLQ" (see the
attached pictures). The following two pictures (JConsole) are taken after the AMQ was started
and all previous messages and statistics where deleted during startup. 
> The error happens with LevelDB and ReplicatedLevelDB. It does not occur if KahaDB is
used. Furthermore the error does not occure if useCache is true and only a couple of messages
are sent. It does occur with useCache is true if many messages are sent. It always happens
if useCache is set to false.
> Endpoint URI and Parameters: activemq:queue:Retry?preserveMessageQos=true 
> We also set the JMSExpiration header to 60 seconds in the future. 

This message was sent by Atlassian JIRA

View raw message