[ARTEMIS-746] Messages sent to a jms topic address are not expiring and are remaining in the queue of core api consumer

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 1.1.0
• Component/s: Broker

Environment

Redhat Linux 6.2

• Assignee: Unassigned
• Reporter: Ruben Cala
• Created: 21/Sep/16 17:50
• Updated: 22/Sep/16 18:57
• Resolved: 22/Sep/16 18:57

Description

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: