Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Tue, 24 Jul 2012 19:53:35 +0000 (UTC)
From: "Timothy Bish (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <2072426101.97876.1343159615431.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <1521953151.96305.1343148216317.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (AMQ-3942) Certain messages do not expire in the
 embedded broker
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Timothy Bish commented on AMQ-3942:
-----------------------------------

Can you try your test against a 5.7-SNAPSHOT broker?  I ran it here a few times and it passed every time.
                
> Certain messages do not expire in the embedded broker
> -----------------------------------------------------
>
>                 Key: AMQ-3942
>                 URL: https://issues.apache.org/jira/browse/AMQ-3942
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.4.3, 5.6.0
>         Environment: Red Hat Enterprise Linux Server release 6.1 (Santiago)
>            Reporter: Pedro de Lara
>              Labels: expiration, timetolive, ttl
>         Attachments: ExpirationTest.java
>
>
> When sending messages to a queue and waiting for the expiration task to expire them, only some of the expired messages are moved to the DLQ. Other expired messages (With same expiration time as the ones moved to the DLQ) just sit in the queue, stuck until all messages in the queue expire, at which point they are all moved to the DLQ.
> This seems to happen only in the embedded broker (configured in activemq.xml) and only for some messages (It seems the size of the message however I am uncertain if the content could actually cause such an issue).
> A Unit Test is provided that shows the issue. The unit test includes a boolean that can be changed to run it towards a created broker (instead of the embedded one) for comparison purposes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira