[ https://issues.apache.org/jira/browse/ARTEMIS-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ruben Cala closed ARTEMIS-746. ------------------------------ Resolution: Duplicate Dup of ARTEMIS-745 > Messages sent to a jms topic address are not expiring and are remaining in > the queue of core api consumer > --------------------------------------------------------------------------------------------------------- > > Key: ARTEMIS-746 > URL: https://issues.apache.org/jira/browse/ARTEMIS-746 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker > Affects Versions: 1.1.0 > Environment: Redhat Linux 6.2 > Reporter: Ruben Cala > > I am pushing messages to a jms topic address (jms.topic.<address>) on a > standalone server. The publisher is using core api. Two consumers, one using > core api, the other using generic stomp protocol. The core api consumer > creates a temporary queue to get the messages from the address. The stomp > client relies on the temporary queue created for it by the broker via the jms > topic functionality. To test slow client scenarios, both consumers are not > acknowledging the messages received. > In jconsole for the queues, I see the MessageCount attribute for the stomp > client stay at a low constant number (2), while the MessagesAcknowledged > number climbs with the MessagesAdded attribute, as expected. For the core api > consumer, however, the MessageCount matches the MessagesAdded attribute, > while the MessageCount remains at zero. > I see in artemis.log a null pointer exception: -- This message was sent by Atlassian JIRA (v6.3.4#6332)