activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AMQ-2017) Topic slow consumer message discarding broken
Date Fri, 08 Jul 2011 21:55:17 GMT

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

Timothy Bish closed AMQ-2017.
-----------------------------

    Resolution: Incomplete

Not test case given to reproduce the issue.

> Topic slow consumer message discarding broken
> ---------------------------------------------
>
>                 Key: AMQ-2017
>                 URL: https://issues.apache.org/jira/browse/AMQ-2017
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.2.0
>            Reporter: Teemu Torma
>             Fix For: NEEDS_REVIEWED
>
>
> TopicSubscription class misbehaves when dispatching matched messages after the first
message has been discarded.  The problem is that difference between dispatch and dequeue counters
is used to determine if the dispatch queue is full, but discarding messages also increments
dequeue counter, breaking the dispatching logic.  Effectively every other message is dispatched
anyway to the consumer side.
> The mismatch in counting can also be observed in jconsole; the topic dispatched queue
size starts ticking down for every discarded message.
> A quick test shows that not incrementing dequeue counter in discard method fixes this
problem, but I don't know if it has any other side effects.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message