activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "SuoNayi (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (AMQ-4261) Please change logging message from INFO to WARN or ERROR when persistent store is full
Date Fri, 18 Jan 2013 09:16:16 GMT

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

SuoNayi edited comment on AMQ-4261 at 1/18/13 9:15 AM:
-------------------------------------------------------

Hi,only logging these events may not help you to quickly react.
When the store is full producers can fail when sending more messages if you enable sendFailIfNoSpace
option.
Furthermore you may want to receive a warning when this happens rather than manual checking
logs on the production servers.
You can subscribe Advisory topic for such events and then publish warnings.
                
      was (Author: wangyin):
    Hi,only logging these events may not help you to quickly react.
When the store is full producers can fail when sending more messages if you enable sendFailIfNoSpace
option.
Furthermore you may want to receive a warning when this happens rather than manual checking
logs on the production servers.
You can subscribe Advisory topic for such events and publish warnings.
                  
> Please change logging message from INFO to WARN or ERROR when persistent store is full

> ---------------------------------------------------------------------------------------
>
>                 Key: AMQ-4261
>                 URL: https://issues.apache.org/jira/browse/AMQ-4261
>             Project: ActiveMQ
>          Issue Type: Improvement
>    Affects Versions: 5.5.1
>            Reporter: Vincent Gao
>
> We use KahaDB for ActiveMQ persistence.  When queue's persistent store is full, a message
such as the following is logged at the INFO level.
> We'd like to request the message to be logged at the ERROR or WARN level.  This is because
production systems typically configures loggers to display messages at WARN level.  A situation
such as this gets into deadlock and makes the application unusable.  Displaying the message
at the ERROR or WARN
> level will provide visibility about the issue for typical production usage.
> 2013-01-17 10:56:28,563 | INFO  | iveMQ Task-37644 | Queue                          
 | 118 - org.apache.activemq.activemq-core - 5.5.1.fuse-7-061 | Usage
> (default:store:queue://xrm-BundleStagingQ:store) percentUsage=99%, usage=1094475857,
limit=1073741824, percentUsageMinDelta=1%;Parent:Usage(default:store)
> percentUsage=101%, usage=1094475857, limit=1073741824, percentUsageMinDelta=1%: Persistent
store is Full, 100% of 1073741824. Stopping producer (ID:vlcov
> 46.fmr.com-47345-1358284999111-4:6:2548:1) to prevent flooding queue://xrm-BundleStagingQ.
See http://activemq.apache.org/producer-flow-control.html for m
> ore info (blocking for: 29828s)

--
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

Mime
View raw message