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

ASF GitHub Bot commented on AMQ-6636:
-------------------------------------

GitHub user alaendle opened a pull request:

    https://github.com/apache/activemq/pull/230

    Unit test illustrating AMQ-6636.

    Hope this is the right way to contribute.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/alaendle/activemq master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq/pull/230.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #230
    
----
commit 3512a5e034f00e928695302d4be14a145ca6bb9b
Author: Andreas Ländle <[email protected]>
Date:   2017-03-23T06:54:22Z

    Provided unit test illustrating AMQ-6636.

commit c3fd6f3713d1d724c9ea5f32669dbf87876cc9c1
Author: Andreas Ländle <[email protected]>
Date:   2017-03-23T06:54:22Z

    Provided unit test illustrating AMQ-6636.

commit 45314722296efc633f3b3444c5808127dd780c30
Author: Andreas Ländle <[email protected]>
Date:   2017-03-23T07:01:52Z

    Provided unit test illustrating AMQ-6636.

----


> Pending Queue Size of durable subscribers 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: 2017-03-22_12h28_44.png, 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 durable subscriber
> c) Press ctrl+c to exit the consumer - and create the offline durable 
> subscription
> d) Publish 2000 message via "ant producer -Ddurable=true 
> -Durl=tcp://localhost:61616 -Dtopic=true -Dsubject=MYSUB"
> Expected result:
> "Pending Queue Size" of the corresponding Offline Durable Topic Subscriber 
> should reach 0 (at least after a few seconds)
> Actual result:
> "Pending Queue Size" shows a value like 1752 and never decreases (see 
> attached screenshot).
> 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)

Reply via email to