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

[Miroslav Novak (Jira)]

     [ https://issues.jboss.org/browse/WFWIP-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Miroslav Novak updated WFWIP-134:
---------------------------------
    Steps to Reproduce: 
{code}
git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
cd eap-tests-hornetq/scripts/
git checkout 7a29c18129937a7973b531f5c4f94826841d0985
groovy -DEAP_ZIP_URL=https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messaging-testing-prepare/504/artifact/jboss-eap.zip PrepareServers7.groovy
export WORKSPACE=$PWD
export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap
export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap
export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap
export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap
cd ../jboss-hornetq-testsuite/
mvn clean test -Dtest=GlobalMemoryAndDiskUsageTestCase#testNoStorageWarnLogWhenProducerBlockOnMaxMemorySize    -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1541405981-ehsavoie-WFLY-10326-SNAPSHOT | tee log
{code}


> Bad WARN messages: AMQ222211: Storage is back to stable now...
> --------------------------------------------------------------
>
>                 Key: WFWIP-134
>                 URL: https://issues.jboss.org/browse/WFWIP-134
>             Project: WildFly WIP
>          Issue Type: Bug
>          Components: Artemis
>            Reporter: Miroslav Novak
>            Assignee: Martyn Taylor
>            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.12.1#712002)