[jboss-jira] [JBoss JIRA] (WFWIP-134) Bad WARN messages: AMQ222211: Storage is back to stable now...

[Brian Stansberry (Jira)]

    [ https://issues.redhat.com/browse/WFWIP-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13949541#comment-13949541 ] 

Brian Stansberry commented on WFWIP-134:
----------------------------------------

[~ehugonnet] Please link this to the EAP7 for a still WIP feature being developed on a topic branch, or move it to another issue tracker like JBEAP that tracks work on the main code branches. Or resolve if out of date.

> Bad WARN messages: AMQ222211: Storage is back to stable now...
> --------------------------------------------------------------
>
>                 Key: WFWIP-134
>                 URL: https://issues.redhat.com/browse/WFWIP-134
>             Project: WildFly WIP
>          Issue Type: Bug
>          Components: Artemis
>            Reporter: Miroslav Novak
>            Assignee: Francesco Nigro
>            Priority: Major
>
> There are unwanted WARN messages:
> {code}
> 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)
> 13:47:50,235 WARN  [org.apache.activemq.artemis.core.server] (Thread-0 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5 at 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
> 13:47:52,642 WARN  [org.apache.activemq.artemis.core.server] (Thread-4 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5 at 371ff371)) AMQ222211: Storage is back to stable now, under max-disk-usage.
> 13:47:57,642 WARN  [org.apache.activemq.artemis.core.server] (Thread-15 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5 at 371ff371)) AMQ222211: Storage is back to stable now, under max-disk-usage.
> ...
> {code}
> 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.13.8#713008)