Getting meesage like Destination address=<Queuname> is blocked

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Getting meesage like Destination address=<Queuname> is blocked

dharmendra
Hi Team ,

I am migrating Artemis 2.4.0 to 2.9.0 and did all configuration and
successfully up but i am getting message continuously
Destination address=<QueueName> is blocked If the system is configured to
block make sure you consume messages on this configuration. which is
restricting message to put in queue and system got hang. below is broker.xml
configuration which is same as in 2.4.0 version
 <journal-min-files>10</journal-min-files>
  <connectors>      
                  <connector name="netty"
>tcp://${activemq.remoting.netty.host:localhost}:${activemq.remoting.netty.port:5445}?useEpoll=true</connector>
                  <connector name="netty-throughput"
>tcp://${activemq.remoting.netty.host:localhost}:${activemq.remoting.netty.port:5455}?useEpoll=true</connector>
      </connectors>
       
      <acceptors>
                <acceptor name="netty"
>tcp://${activemq.remoting.netty.host:localhost}:${activemq.remoting.netty.port:5445}?useEpoll=true</acceptor>
                <acceptor name="netty-throughput"
>tcp://${activemq.remoting.netty.host:localhost}:${activemq.remoting.netty.port:5455}?useEpoll=true</acceptor>
      </acceptors>


 <security-settings>
    <security-setting match="#">
      <permission type="createNonDurableQueue" roles="amq"/>
      <permission type="deleteNonDurableQueue" roles="amq"/>
      <permission type="createDurableQueue" roles="amq"/>
      <permission type="deleteDurableQueue" roles="amq"/>
      <permission type="createAddress" roles="amq"/>
      <permission type="deleteAddress" roles="amq"/>
      <permission type="consume" roles="amq"/>
      <permission type="browse" roles="amq"/>
      <permission type="send" roles="amq"/>
      <permission type="manage" roles="amq"/>
    </security-setting>
  </security-settings>
  <address-settings>
    <address-setting match="#">
      <dead-letter-address>DLQ</dead-letter-address>
      <expiry-address>ExpiryQueue</expiry-address>
      <redelivery-delay>0</redelivery-delay>
      <max-size-bytes>10737418240</max-size-bytes>
     
<message-counter-history-day-limit>10</message-counter-history-day-limit>
      <address-full-policy>PAGE</address-full-policy>
      <auto-create-queues>true</auto-create-queues>
      <auto-create-addresses>true</auto-create-addresses>
      <auto-create-jms-queues>false</auto-create-jms-queues>
      <auto-create-jms-topics>false</auto-create-jms-topics>
      <auto-delete-queues>false</auto-delete-queues>
      <max-delivery-attempts>-1</max-delivery-attempts>
    </address-setting>
  </address-settings>

Please suggest me why i am getting above message which is causing problem to
block Queues. Please help me out.
Thanks
Dharmendra



-----
DKumar
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html
DKumar
Reply | Threaded
Open this post in threaded view
|

Re: Getting meesage like Destination address=<Queuname> is blocked

wei yang
Is your disk full on broker side?

dharmendra <[hidden email]> 于2019年10月17日周四 下午8:15写道:

> Hi Team ,
>
> I am migrating Artemis 2.4.0 to 2.9.0 and did all configuration and
> successfully up but i am getting message continuously
> Destination address=<QueueName> is blocked If the system is configured to
> block make sure you consume messages on this configuration. which is
> restricting message to put in queue and system got hang. below is
> broker.xml
> configuration which is same as in 2.4.0 version
>  <journal-min-files>10</journal-min-files>
>   <connectors>
>                   <connector name="netty"
>
> >tcp://${activemq.remoting.netty.host:localhost}:${activemq.remoting.netty.port:5445}?useEpoll=true</connector>
>                   <connector name="netty-throughput"
>
> >tcp://${activemq.remoting.netty.host:localhost}:${activemq.remoting.netty.port:5455}?useEpoll=true</connector>
>       </connectors>
>
>       <acceptors>
>                 <acceptor name="netty"
>
> >tcp://${activemq.remoting.netty.host:localhost}:${activemq.remoting.netty.port:5445}?useEpoll=true</acceptor>
>                 <acceptor name="netty-throughput"
>
> >tcp://${activemq.remoting.netty.host:localhost}:${activemq.remoting.netty.port:5455}?useEpoll=true</acceptor>
>       </acceptors>
>
>
>  <security-settings>
>     <security-setting match="#">
>       <permission type="createNonDurableQueue" roles="amq"/>
>       <permission type="deleteNonDurableQueue" roles="amq"/>
>       <permission type="createDurableQueue" roles="amq"/>
>       <permission type="deleteDurableQueue" roles="amq"/>
>       <permission type="createAddress" roles="amq"/>
>       <permission type="deleteAddress" roles="amq"/>
>       <permission type="consume" roles="amq"/>
>       <permission type="browse" roles="amq"/>
>       <permission type="send" roles="amq"/>
>       <permission type="manage" roles="amq"/>
>     </security-setting>
>   </security-settings>
>   <address-settings>
>     <address-setting match="#">
>       <dead-letter-address>DLQ</dead-letter-address>
>       <expiry-address>ExpiryQueue</expiry-address>
>       <redelivery-delay>0</redelivery-delay>
>       <max-size-bytes>10737418240</max-size-bytes>
>
> <message-counter-history-day-limit>10</message-counter-history-day-limit>
>       <address-full-policy>PAGE</address-full-policy>
>       <auto-create-queues>true</auto-create-queues>
>       <auto-create-addresses>true</auto-create-addresses>
>       <auto-create-jms-queues>false</auto-create-jms-queues>
>       <auto-create-jms-topics>false</auto-create-jms-topics>
>       <auto-delete-queues>false</auto-delete-queues>
>       <max-delivery-attempts>-1</max-delivery-attempts>
>     </address-setting>
>   </address-settings>
>
> Please suggest me why i am getting above message which is causing problem
> to
> block Queues. Please help me out.
> Thanks
> Dharmendra
>
>
>
> -----
> DKumar
> --
> Sent from:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html
>
Reply | Threaded
Open this post in threaded view
|

Re: Getting meesage like Destination address=<Queuname> is blocked

dharmendra
Thank you for replying.
But disk is not full. I am surprised that for this blocked issue. Is there
any other issue apart from disk. Please suggest.



-----
DKumar
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html
DKumar
Reply | Threaded
Open this post in threaded view
|

Re: Getting meesage like Destination address=<Queuname> is blocked

wei yang
Can you use the Jmx Jconsole('getAddressSettingsAsJSON' in
ActiveMqServerControlImpl mbean) to see if addressFullMessagePolicy is
indeed PAGE as in the broker.xml?

If it's PAGE, can you provider details on which protocol and version of
client you are using?

dharmendra <[hidden email]> 于2019年10月18日周五 下午5:01写道:

> Thank you for replying.
> But disk is not full. I am surprised that for this blocked issue. Is there
> any other issue apart from disk. Please suggest.
>
>
>
> -----
> DKumar
> --
> Sent from:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html
>