Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-7827

Default production profile configuration uses BLOCK address full policy but this full address policy is not recommended in production

XMLWordPrintable

    • Not Required
    • NEW

      Default production profile uses BLOCK address full policy but this policy is not recommended in production (since EAP 5.1.2 CR2 build). Default configuration profile should use recommended configuration values.

      Current production profile EAP 5.1.2 CR3:

         <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>60000</redelivery-delay>
               <max-size-bytes>10485760</max-size-bytes>       
               <message-counter-history-day-limit>10</message-counter-history-day-limit>
               <address-full-policy>BLOCK</address-full-policy>
            </address-setting>
         </address-settings>
      

      See
      http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html-single/HornetQ_User_Guide/index.html#paging
      Section 22.5. Blocking producers

              csuconic@redhat.com Clebert Suconic
              pslavice@redhat.com Pavel Slavicek
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: