[jira] [Commented] (ARTEMIS-2283) Bad WARN messages: AMQ222211: Storage is back to stable now...

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on ARTEMIS-2283:
----------------------------------------------------------

Commit ac4cd4856c386c4cd824a56b68c6c34a2a1aab6c in activemq-artemis's branch refs/heads/master from Francesco Nigro
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=ac4cd48 ]

ARTEMIS-2283 Bad WARN message "AMQ222211: Storage is back to stable now"

LocalMonitor::under on PagingManagerImpl won't log anymore with a
warning message if the producers got unblocked and with info
if disk it getting freed


> Bad WARN messages: AMQ222211: Storage is back to stable now...
> --------------------------------------------------------------
>
>                 Key: ARTEMIS-2283
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2283
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 2.7.0
>            Reporter: Emmanuel Hugonnet
>            Priority: Major
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> There are unwanted WARN messages:
>  
> |{color:#000000}13:47:48,158 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 15.0.0.Alpha1-SNAPSHOT (WildFly Core 7.0.0.Alpha4) started in 8017ms - Started 495 of 723 services (489 services are lazy, passive or on-demand){color}|
> |{color:#000000}13:47:50,235 WARN  [org.apache.activemq.artemis.core.server] (Thread-0 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@371ff371)) AMQ222183: Blocking message production on address 'jms.queue.InQueue'; size is currently: 10,635,300 bytes; max-size-bytes on address: 10,485,760, global-max-size is 10,635,300{color}|
> |{color:#000000}13:47:52,642 WARN  [org.apache.activemq.artemis.core.server] (Thread-4 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@371ff371)) AMQ222211: Storage is back to stable now, under max-disk-usage.{color}|
> |{color:#000000}13:47:57,642 WARN  [org.apache.activemq.artemis.core.server] (Thread-15 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@371ff371)) AMQ222211: Storage is back to stable now, under max-disk-usage.{color}|
> |{color:#000000}... {color}|
>  
> when server has configured {{global-max-memory-size}} and address-full-policy to BLOCK. Once {{global-max-memory-size}} then starts to log above warnings which with max-disk-usage. Which is not correct as no disk limitation was reached.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)