[jira] [Resolved] (ARTEMIS-745) Messages sent to a jms topic address are not expiring in temporary queue created via core API

["Justin Bertram (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARTEMIS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Bertram resolved ARTEMIS-745.
------------------------------------
    Resolution: Cannot Reproduce

> Messages sent to a jms topic address are not expiring in temporary queue created via core API
> ---------------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-745
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-745
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 1.1.0
>         Environment: Redhat Linux 6.2
>            Reporter: Ruben Cala
>            Assignee: Justin Bertram
>
> I am publishing messages to a topic address (jms.topic.<address>).  I set the message expiration to be 2 seconds (publishing via core api).  I have two consumers, one using core api, one using generic stomp protocol.  The core api creates a temporary queue to receive the messages from the  address.  The stomp consumer relies on the auto-generated temporary queue mechanism provided by the broker.  To investigate slow consumer scenarios, both consumers are not acknowledging the messages.
> In JConsole for the stomp consumer, its queue MessagesAcknowledged attribute count rises, while the MessageCount stays constant with the MessagesAdded count (low number around 5 usually).
> For the core api consumer, however, its queue MessagesAcknowledged attribute count stays at 0, while its MessageCount attribute increases with the MessagesAdded number.  This eventually causes the broker to run out of memory.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)