Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Mon, 23 Nov 2015 02:12:10 +0000 (UTC)
From: "Nevin Chen (JIRA)" <jira@apache.org>
To: issues@activemq.apache.org
Message-ID: <JIRA.12761704.1418634920000.154498.1448244730954@Atlassian.JIRA>
In-Reply-To: <JIRA.12761704.1418634920000@Atlassian.JIRA>
References: <JIRA.12761704.1418634920000@Atlassian.JIRA>
 <JIRA.12761704.1418634920550@arcas>
Subject: [jira] [Commented] (AMQ-5489) JMSExpiration not working correctly
 with LevelDB
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AMQ-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15021377#comment-15021377 ] 

Nevin Chen commented on AMQ-5489:
---------------------------------

Hi, for me, I didn't set the deleteAllMessagesOnStartup property in activemq.xml. I just use the default activemq.xml The default value should be false. I don't think this is the cause. Maybe my case is different from the reporter's.

> JMSExpiration not working correctly with LevelDB
> ------------------------------------------------
>
>                 Key: AMQ-5489
>                 URL: https://issues.apache.org/jira/browse/AMQ-5489
>             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, activemq.xml, jms-expiration-test.zip
>
>
> 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
(v6.3.4#6332)