5 Replies Latest reply on Nov 11, 2011 11:34 AM by Andy Taylor

    problem with Paging/Drop address full policy on jms topic

    Daniel Zietz Newbie

      We have some problems with JMS Topics provided by HornetQ 2.2.2 integrated in Jboss AS 5 on a production server:

       

       

      - If address-full-policy is configured to use "PAGING", HornetQ does not delete page files even if all messages are consumed. This fills harddisk till no space is available anymore and jboss stops working.(This may be related to https://issues.jboss.org/browse/HORNETQ-529)

      - if address-full-policy is configured to use "DROP" the topic stops accepting messages after some time(i.e. the value of "Messages Added" in the managment interface does not increment anymore and no more messages are delivered)

       

      The topic receives about 500-700 messages per minute and deliveres them to an average of 10 consumers.

      It is likely that the client connections are terminated by network errors quite often.

      Nevertheless the only logging I found referring this is "WARN  [org.hornetq.core.server.impl.ServerSessionImpl] [T:248] Client connection failed, clearing up resources for session f1813b6e-0af1-11e1-bf3f-001f3b211d7d".

       

      The configuration of the topic in hornetq-jms.xml looks like this:

       


      <topic name="events.notifications">

      <entry name="/topic/events.notifications"/> 

      </topic>

       

      And the configuration of address-full-policy in hornetq-configuration looks like this:

       


         <address-settings>

        <!--default for catch all-->
        <address-setting match="#">
           <dead-letter-address>jms.queue.DLQ</dead-letter-address>
           <expiry-address>jms.queue.ExpiryQueue</expiry-address>
           <redelivery-delay>0</redelivery-delay>
           <max-size-bytes>50000000</max-size-bytes>  
           <message-counter-history-day-limit>10</message-counter-history-day-limit>
           <page-size-bytes>100000</page-size-bytes>
      <address-full-policy>DROP</address-full-policy>
        </address-setting>
        
       

         </address-settings>

       

      First tests showed that the paging problem might not appear with HornetQ 2.2.8, but since the problem is only randomly reproduceable on local installations this is not for sure.

       

      Therefore I would be thankful for every tip (e.g. configuration problems) that could help to solve this problem.