AMQ 7.8 page-size-bytes attribute does not use 3rd level address-setting value

Define the address-setting in broker.xml like :  <address-setting match= "test.#" > <dead-letter-address> test.DLQ </dead-letter-address> <expiry-address> test.ExpiryQueue </expiry-address> <redelivery-delay> 0 </redelivery-delay> <max-size-bytes> 1MB </max-size-bytes> <page-size-bytes> 100KB </page-size-bytes> </address-setting> <address-setting match= "test.foo.#" > <dead-letter-address> test.DLQ </dead-letter-address> </address-setting> <address-setting match= "test.foo.bar" > <dead-letter-address> test.foo.DLQ </dead-letter-address> </address-setting> Address like : <address name= "test.foo.bar" > <anycast> <queue name= "test.foo.bar" > <durable> true </durable> </queue> </anycast> </address> Start the broker. It fails to deploy the address  test.foo.bar with warn (multiple restart throws ERROR message) 2021-01-07 16:13:31,954 WARN [org.apache.activemq.artemis.core.server] AMQ222275: Failed to deploy queue test.foo.bar: java.lang.IllegalStateException: pageSize for address test.foo.bar >= maxSize. Normally pageSize should be significantly smaller than maxSize, ms: 1048576 ps 10485760  Stop the broker. Clear data dir and remove the address-setting "test.foo.bar" from broker.xml. Restart the broker. This time address  test.foo.bar deploys with page-size-bytes 100KB defined in "test.#". Stop the broker. Again use the address-setting defined in step-1. Just modify the max-size-bytes value greater than 10 MB or -1 in address-setting "test.#" and restart the broker. Address test.foo.bar" deploys with page-size-bytes 10485760 i.e default value.  This shows max-size-bytes follows address-setting hierarchies. However page-size-bytes not.