[ 
https://issues.apache.org/jira/browse/AMQ-9153?focusedWorklogId=822296&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-822296
 ]

ASF GitHub Bot logged work on AMQ-9153:
---------------------------------------

                Author: ASF GitHub Bot
            Created on: 01/Nov/22 13:07
            Start Date: 01/Nov/22 13:07
    Worklog Time Spent: 10m 
      Work Description: cshannon commented on PR #927:
URL: https://github.com/apache/activemq/pull/927#issuecomment-1298482028

   > LGTM from a code standpoint. I'm doing a quick test.
   
   The advisory is off by default anyways and I doubt a lot of people use it. 
It's pretty spammy if you turn it on as it fires whenever prefetch is full 
(durable subs is the same way). The fact that no one complained in 10 years (or 
at least I don't recall but maybe someone created a Jira or posted on the 
mailing list) tells me there's probably not a lot of people that care.




Issue Time Tracking
-------------------

    Worklog Id:     (was: 822296)
    Time Spent: 20m  (was: 10m)

> Fix Slow Consumer Advisory for Queue subscriptions
> --------------------------------------------------
>
>                 Key: AMQ-9153
>                 URL: https://issues.apache.org/jira/browse/AMQ-9153
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.17.2
>            Reporter: Christopher L. Shannon
>            Assignee: Christopher L. Shannon
>            Priority: Major
>             Fix For: 5.18.0, 5.17.3
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The {{AdvisoryTests}} class was not running due to a bug with the the test 
> configuration that is now fixed in AMQ-9152. The {{testSlowConsumerAdvisory}} 
> test is now failing when run so this needs to be investigated to see if it's 
> a real failure and something broke or if the test needs to be fixed.
> After further investigation it turns out after changse in AMQ-1902 it no 
> longer works at all for queues (only durables and topic subs) so it needs to 
> be fixed.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to