[
https://issues.apache.org/jira/browse/AMQ-9712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Livingston updated AMQ-9712:
---------------------------------
Description:
When using AMQP, the ActiveMQ broker does not seem to be reporting a
_PrefetchSize_ which I would expect to represents the client's set credit
window. The result of this is that the broker's functionality to detect "slow
consumers" becomes inactive and the triggers to a _SlowConsumerStrategy_ are
never met.
Is this the expected behavior and/or a limitation of the AMQP protocol?
_TopicSubscription.add(...)_ will only mark a slow consumer if
_ConsumerInfo.prefetchSize_ > 1{_}.{_}
*An example of the reported PrefetchSize by querying the consumer information
via CLI (in this the case the consumer credit window = 10):*
{code:java}
Connection =
org.apache.activemq:type=Broker,brokerName=localhost,connector=clientConnectors,connectorName=amqp,connectionViewType=clientId,connectionName=ID_7a0a3b25-fb5b-445b-9a54-b7756e0a3d47_1_1
PendingQueueSize = 0
MessageCountAwaitingAcknowledge = 0
PrefetchSize = 0
Active = true
MaximumPendingQueueSize = 5000
{code}
was:
When using AMQP, the ActiveMQ broker does not seem to be reporting a
_PrefetchSize_ which I would expect to represents the client's set credit
window. The result of this is that the broker's functionality to detect "slow
consumers" becomes inactive and the triggers to a _SlowConsumerStrategy_ are
never called.
Is this the expected behavior and/or a limitation of the AMQP protocol?
_TopicSubscription.add(...)_ will only mark a slow consumer if
_ConsumerInfo.prefetchSize_ > 1{_}.{_}
*An example of the reported PrefetchSize by querying the consumer information
via CLI (in this the case the consumer credit window = 10):*
{code:java}
Connection =
org.apache.activemq:type=Broker,brokerName=localhost,connector=clientConnectors,connectorName=amqp,connectionViewType=clientId,connectionName=ID_7a0a3b25-fb5b-445b-9a54-b7756e0a3d47_1_1
PendingQueueSize = 0
MessageCountAwaitingAcknowledge = 0
PrefetchSize = 0
Active = true
MaximumPendingQueueSize = 5000
{code}
> AMQP PrefetchSize is always zero (AMQP slow consumers)
> ------------------------------------------------------
>
> Key: AMQ-9712
> URL: https://issues.apache.org/jira/browse/AMQ-9712
> Project: ActiveMQ Classic
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 5.18.3
> Reporter: Ryan Livingston
> Priority: Minor
>
> When using AMQP, the ActiveMQ broker does not seem to be reporting a
> _PrefetchSize_ which I would expect to represents the client's set credit
> window. The result of this is that the broker's functionality to detect "slow
> consumers" becomes inactive and the triggers to a _SlowConsumerStrategy_ are
> never met.
> Is this the expected behavior and/or a limitation of the AMQP protocol?
> _TopicSubscription.add(...)_ will only mark a slow consumer if
> _ConsumerInfo.prefetchSize_ > 1{_}.{_}
> *An example of the reported PrefetchSize by querying the consumer information
> via CLI (in this the case the consumer credit window = 10):*
> {code:java}
> Connection =
> org.apache.activemq:type=Broker,brokerName=localhost,connector=clientConnectors,connectorName=amqp,connectionViewType=clientId,connectionName=ID_7a0a3b25-fb5b-445b-9a54-b7756e0a3d47_1_1
> PendingQueueSize = 0
> MessageCountAwaitingAcknowledge = 0
> PrefetchSize = 0
> Active = true
> MaximumPendingQueueSize = 5000
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org
For additional commands, e-mail: issues-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
