[jira] [Commented] (AMQ-6084) Have an option to error out if a limit is exceeded

["Martin Lichtin (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMQ-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185668#comment-15185668 ] 

Martin Lichtin commented on AMQ-6084:
-------------------------------------

Nice feature! Would be great to have it documented on http://activemq.apache.org/

> Have an option to error out if a limit is exceeded
> --------------------------------------------------
>
>                 Key: AMQ-6084
>                 URL: https://issues.apache.org/jira/browse/AMQ-6084
>             Project: ActiveMQ
>          Issue Type: Sub-task
>          Components: Broker
>    Affects Versions: 5.13.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.13.1, 5.14.0
>
>
> If a broker exits due to no space {code}   <ioExceptionHandler>
> 	      <defaultIOExceptionHandler ignoreNoSpaceErrors="false"/>
> 	  </ioExceptionHandler>{code} i.e: some other process uses disk space. On a restart it will reset the limits and block pending space. Flow control will kick in. It may not be possible to consume messages in this stage. 
> However it will not allow clients to failover to another broker.
> I think we should have an option to force the broker to error out, or fail to start if limits are set and they cannot be satisfied.
> This will ensure that the broker will not accept connections in that state.
> it could be{code}<broker adjustUsageLimits="false" ..>{code}
> When false, if the limits are exceeded, store usage or memory usage - the broker fails to start. When true, it adjusts them (like today) to what is available.
> As ever, naming things is hard. Any better name? 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)