[
https://issues.apache.org/jira/browse/AMQ-6854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16236016#comment-16236016
]
ASF subversion and git services commented on AMQ-6854:
------------------------------------------------------
Commit b29ccf348803249b9d62cc607a8c7e22f06cf8a5 in activemq's branch
refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=b29ccf3 ]
[AMQ-6854] log warn if page in is blocked on usage preventing dispatch. Reuse
blockedProducerWarningInterval to tweak reporting
> Log a warning if paging in for queues blocks on usage constraints
> -----------------------------------------------------------------
>
> Key: AMQ-6854
> URL: https://issues.apache.org/jira/browse/AMQ-6854
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 5.15.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Minor
> Fix For: 5.16.0
>
>
> In a case where the cache is disabled but there is no flow control, messages
> can continue to be produced directly to the store. Dispatch from memory will
> continue and paging in will work in the normal way.
> However it is possible for queues to starve each other when paging in, such
> that some queues with no messages in memory will not be able to page in.
> In this case, it is important that we log a warning to have some indication
> in the logs that consumers may be starved such that memory limits can be
> increased if necessary.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
