[jira] [Updated] (AMQ-6636) Pending Queue Size of durable subsribers isn't correct - or message expiration doesn't work

["Andreas Ländle (JIRA)" <ji...@apache.org>]

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

Andreas Ländle updated AMQ-6636:
--------------------------------
    Attachment: activemq.xml
                activemq.xml.patch

> Pending Queue Size of durable subsribers isn't correct - or message expiration doesn't work
> -------------------------------------------------------------------------------------------
>
>                 Key: AMQ-6636
>                 URL: https://issues.apache.org/jira/browse/AMQ-6636
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.14.4
>         Environment: Windows 7, 64 Bit, Java 1.8.0-101
>            Reporter: Andreas Ländle
>         Attachments: activemq.xml, activemq.xml.patch
>
>
> I use expireMessagesPeriod="100" for topics and the timestamp-plugin with a TTL of 1s. 
> If I publish messages the "Pending Queue Size" of a offline duracle subscriber never reaches 0 (in real life it increases steadily).
> Steps to reproduce:
> a) Start a clean/fresh activemq 5.14.4 broker instance with the attached activemq.xml configuration (or adapt the default configuration to use expireMessagesPeriod and timeStampBrokerPlugin - see also patch file)
> b) Use "ant consumer -Durl=tcp://localhost:61616 -Dtopic=true -Dsubject=MYSUB -Ddurable=true" to create topic and durble subscriber
> c) Press ctrl+c to exit the consumer - and create the offline duracle subscription
> d) Publish 2000 message via "ant producer -Ddurable=true -Durl=tcp://localhost:61616 -Dtopic=true -Dsubject=MYSUB"
> Expected result:
> "Pending Queue Size" should reach 0 (at least after a few seconds)
> Actual result:
> "Pending Queue Size" shows a value like 1752 and never decreases.
> Please let me know if you are able to reproduce the problem and if/how I can contribute.



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