[jira] [Commented] (ARTEMIS-1732) AMQP anonymous producer not blocked on max-disk-usage
[ https://issues.apache.org/jira/browse/ARTEMIS-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16566295#comment-16566295 ] ASF subversion and git services commented on ARTEMIS-1732: -- Commit f2198ae5d79d48a9783f8da4da8d7c28836fd2be in activemq-artemis's branch refs/heads/2.6.x from Clebert Suconic [ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=f2198ae ] ARTEMIS-1732 Fixing AMQPSenderTest (cherry picked from commit e290071ceddd3ac66f23ab537e3e400ddd25bdf1) > 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)
[jira] [Commented] (ARTEMIS-1732) AMQP anonymous producer not blocked on max-disk-usage
[ https://issues.apache.org/jira/browse/ARTEMIS-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16566261#comment-16566261 ] ASF subversion and git services commented on ARTEMIS-1732: -- Commit e290071ceddd3ac66f23ab537e3e400ddd25bdf1 in activemq-artemis's branch refs/heads/master from Clebert Suconic [ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=e290071 ] ARTEMIS-1732 Fixing AMQPSenderTest > 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)
[jira] [Commented] (ARTEMIS-1732) AMQP anonymous producer not blocked on max-disk-usage
[ https://issues.apache.org/jira/browse/ARTEMIS-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16564619#comment-16564619 ] ASF GitHub Bot commented on ARTEMIS-1732: - Github user gaohoward commented on the issue: https://github.com/apache/activemq-artemis/pull/1950 I think it's ok. > 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)
[jira] [Commented] (ARTEMIS-1732) AMQP anonymous producer not blocked on max-disk-usage
[ https://issues.apache.org/jira/browse/ARTEMIS-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16564609#comment-16564609 ] ASF GitHub Bot commented on ARTEMIS-1732: - Github user clebertsuconic commented on the issue: https://github.com/apache/activemq-artemis/pull/1950 @michaelandrepearce @gaohoward merged with an additional fix. if there's any change you like I can add an additional PR. if you could review please? > 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)
[jira] [Commented] (ARTEMIS-1732) AMQP anonymous producer not blocked on max-disk-usage
[ https://issues.apache.org/jira/browse/ARTEMIS-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16564608#comment-16564608 ] 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)
[jira] [Commented] (ARTEMIS-1732) AMQP anonymous producer not blocked on max-disk-usage
[ 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)
[jira] [Commented] (ARTEMIS-1732) AMQP anonymous producer not blocked on max-disk-usage
[ https://issues.apache.org/jira/browse/ARTEMIS-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16564604#comment-16564604 ] ASF subversion and git services commented on ARTEMIS-1732: -- Commit 53e1d601601204dc2aa587fcb3046d5c1d6d026d in activemq-artemis's branch refs/heads/master from [~gaohoward] [ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=53e1d60 ] 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. > 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)
[jira] [Commented] (ARTEMIS-1732) AMQP anonymous producer not blocked on max-disk-usage
[ https://issues.apache.org/jira/browse/ARTEMIS-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16564606#comment-16564606 ] ASF GitHub Bot commented on ARTEMIS-1732: - Github user asfgit closed the pull request at: https://github.com/apache/activemq-artemis/pull/1950 > 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)
[jira] [Commented] (ARTEMIS-1732) AMQP anonymous producer not blocked on max-disk-usage
[ https://issues.apache.org/jira/browse/ARTEMIS-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16564605#comment-16564605 ] ASF subversion and git services commented on ARTEMIS-1732: -- Commit 0e36e072bdf0c4636623aacbd15912857770c73f in activemq-artemis's branch refs/heads/master from Clebert Suconic [ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=0e36e07 ] 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. > 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)
[jira] [Commented] (ARTEMIS-1732) AMQP anonymous producer not blocked on max-disk-usage
[ https://issues.apache.org/jira/browse/ARTEMIS-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16564506#comment-16564506 ] ASF GitHub Bot commented on ARTEMIS-1732: - Github user clebertsuconic commented on the issue: https://github.com/apache/activemq-artemis/pull/1950 Actually the test is very nice.. I'm doing some refactoring on this. > 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)
[jira] [Commented] (ARTEMIS-1732) AMQP anonymous producer not blocked on max-disk-usage
[ https://issues.apache.org/jira/browse/ARTEMIS-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16564414#comment-16564414 ] ASF GitHub Bot commented on ARTEMIS-1732: - Github user clebertsuconic commented on the issue: https://github.com/apache/activemq-artemis/pull/1950 The test added is also wrong.. a sender should block while there are no credits instead of holding runnables on the server. > 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)
[jira] [Commented] (ARTEMIS-1732) AMQP anonymous producer not blocked on max-disk-usage
[ https://issues.apache.org/jira/browse/ARTEMIS-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16564409#comment-16564409 ] ASF GitHub Bot commented on ARTEMIS-1732: - Github user clebertsuconic commented on the issue: https://github.com/apache/activemq-artemis/pull/1950 This needs some work on the model before it can be merged. > 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)
[jira] [Commented] (ARTEMIS-1732) AMQP anonymous producer not blocked on max-disk-usage
[ https://issues.apache.org/jira/browse/ARTEMIS-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16564305#comment-16564305 ] ASF GitHub Bot commented on ARTEMIS-1732: - Github user michaelandrepearce commented on the issue: https://github.com/apache/activemq-artemis/pull/1950 @clebertsuconic Whats occuring on this one? We safe to merge this to master now? > 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)
[jira] [Commented] (ARTEMIS-1732) AMQP anonymous producer not blocked on max-disk-usage
[ https://issues.apache.org/jira/browse/ARTEMIS-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16395374#comment-16395374 ] ASF GitHub Bot commented on ARTEMIS-1732: - Github user gaohoward commented on the issue: https://github.com/apache/activemq-artemis/pull/1950 ok > 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.5.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)
[jira] [Commented] (ARTEMIS-1732) AMQP anonymous producer not blocked on max-disk-usage
[ https://issues.apache.org/jira/browse/ARTEMIS-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16395368#comment-16395368 ] ASF GitHub Bot commented on ARTEMIS-1732: - Github user clebertsuconic commented on the issue: https://github.com/apache/activemq-artemis/pull/1950 We will have a 2.5.1 shortly > 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.5.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)
[jira] [Commented] (ARTEMIS-1732) AMQP anonymous producer not blocked on max-disk-usage
[ https://issues.apache.org/jira/browse/ARTEMIS-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16395365#comment-16395365 ] ASF GitHub Bot commented on ARTEMIS-1732: - Github user clebertsuconic commented on the issue: https://github.com/apache/activemq-artemis/pull/1950 Lets leave this out of the release... please don't merge this!!! I will get back to this after the release. > 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.5.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)
[jira] [Commented] (ARTEMIS-1732) AMQP anonymous producer not blocked on max-disk-usage
[ https://issues.apache.org/jira/browse/ARTEMIS-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16395359#comment-16395359 ] ASF GitHub Bot commented on ARTEMIS-1732: - Github user gaohoward commented on the issue: https://github.com/apache/activemq-artemis/pull/1950 @clebertsuconic thanks. > 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.5.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)
[jira] [Commented] (ARTEMIS-1732) AMQP anonymous producer not blocked on max-disk-usage
[ https://issues.apache.org/jira/browse/ARTEMIS-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16395320#comment-16395320 ] ASF GitHub Bot commented on ARTEMIS-1732: - Github user clebertsuconic commented on the issue: https://github.com/apache/activemq-artemis/pull/1950 this is not complete. if your disk is full... and no more producing is happening you will never release the executables. Besides.. I will look if there is a way to use the PagingStoreManager to do this, or to avoid the duplicate code... (which would fix the issue I mentioned) > 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.5.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)
[jira] [Commented] (ARTEMIS-1732) AMQP anonymous producer not blocked on max-disk-usage
[ https://issues.apache.org/jira/browse/ARTEMIS-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16394745#comment-16394745 ] ASF GitHub Bot commented on ARTEMIS-1732: - GitHub user gaohoward opened a pull request: https://github.com/apache/activemq-artemis/pull/1950 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. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gaohoward/activemq-artemis fmq1031 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/1950.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1950 commit 2f471dc67870f0c454efb5f868358afe59c91184 Author: Howard Gao Date: 2018-03-12T02:33:09Z 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. > 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.5.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)
[jira] [Commented] (ARTEMIS-1732) AMQP anonymous producer not blocked on max-disk-usage
[ https://issues.apache.org/jira/browse/ARTEMIS-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16392980#comment-16392980 ] clebert suconic commented on ARTEMIS-1732: -- doesn't seem like done... defer it > 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.5.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)
