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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.7.0
• Component/s: Broker
• Assignee: Unassigned
• Reporter: Emmanuel Hugonnet
• Created: 26/Mar/19 09:53
• Updated: 26/Apr/19 01:13
• Resolved: 26/Apr/19 01:13

Description

There are unwanted WARN messages:

 

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@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@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@371ff371)) AMQ222211: Storage is back to stable now, under max-disk-usage.

...

 

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.

Issue Links

• links to: GitHub Pull Request #2591