You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "clebert suconic (JIRA)" <ji...@apache.org> on 2019/04/26 01:14:01 UTC
[jira] [Closed] (ARTEMIS-2283) Bad WARN messages: AMQ222211:
Storage is back to stable now...
[ https://issues.apache.org/jira/browse/ARTEMIS-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
clebert suconic closed ARTEMIS-2283.
------------------------------------
Resolution: Fixed
> 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: 1h
> 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)