[ https://issues.apache.org/jira/browse/ARTEMIS-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16564607#comment-16564607 ]
ASF subversion and git services commented on ARTEMIS-1732: ---------------------------------------------------------- Commit 73b3ebff1a8c2aef84d2df90eb671258201b9fa4 in activemq-artemis's branch refs/heads/2.6.x from [~gaohoward] [ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=73b3ebf ] ARTEMIS-1732 AMQP anonymous producer not blocked on max-disk-usage Anonymous senders (those created without a target address) are not blocked when max-disk-usage is reached. The cause is that when such a sender is created on the broker, the broker doesn't check the disk/memory usage and gives out the credit immediately. Squashed with: ----- ARTEMIS-1732 I simplified some of the changes performed at the previous commit. Also I changed GlobalDiskFullTest to actually block the senders. I moved the Runnables from PagingManager into the Util as AtomicRunnable. (cherry picked from commit 0e36e072bdf0c4636623aacbd15912857770c73f) (cherry picked from commit 53e1d601601204dc2aa587fcb3046d5c1d6d026d) > AMQP anonymous producer not blocked on max-disk-usage > ----------------------------------------------------- > > Key: ARTEMIS-1732 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1732 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP > Affects Versions: 2.4.0 > Reporter: Howard Gao > Assignee: Howard Gao > Priority: Major > Fix For: 2.7.0 > > > Anonymous senders (those created without a target address) are not blocked > when max-disk-usage is reached. The cause is that when such a sender is > created on the broker, the broker doesn't check the disk/memory usage and > gives out the credit immediately. -- This message was sent by Atlassian JIRA (v7.6.3#76005)