You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/03/26 17:06:00 UTC
[jira] [Work logged] (ARTEMIS-2283) Bad WARN messages: AMQ222211:
Storage is back to stable now...
[ https://issues.apache.org/jira/browse/ARTEMIS-2283?focusedWorklogId=218761&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-218761 ]
ASF GitHub Bot logged work on ARTEMIS-2283:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 26/Mar/19 17:05
Start Date: 26/Mar/19 17:05
Worklog Time Spent: 10m
Work Description: franz1981 commented on pull request #2591: ARTEMIS-2283 Bad WARN message "AMQ222211: Storage is back to stable now"
URL: https://github.com/apache/activemq-artemis/pull/2591
LocalMonitor::under on PagingManagerImpl won't log anymore with a
warning message if the producers got unblocked
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 218761)
Time Spent: 10m
Remaining Estimate: 0h
> 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: 10m
> 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)