I have seen both use cases I think:

  • The code I write prefers losing log messages over blocking.
  • Somebody mentioned (ab?)using logging to create an audit trail in their code; in that case, one would rather block than lose messages.
    So making this configurable would probably be best.

Wholeheartedly agreeing that a queue overrun should be diagnosed, addWarn() seems to be the right way to do that.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira