Bug 1099404 - The HornetQ address settings are not properly inherited
Summary: The HornetQ address settings are not properly inherited
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: JMS
Version: 6.2.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER6
: EAP 6.3.0
Assignee: Jeff Mesnil
QA Contact: Miroslav Novak
Russell Dickenson
URL: https://c.na7.visual.force.com/apex/C...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-20 08:49 UTC by Tom Ross
Modified: 2019-07-11 07:58 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-06-28 15:41:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-3375 0 Major Resolved The HornetQ address settings are not properly inherited 2015-11-02 11:10:37 UTC

Description Tom Ross 2014-05-20 08:49:31 UTC
When using multiple address settings in HornetQ configuration the address setting should be inherited from more generic setting by more specific setting. If two address setting are used like
<address-settings>
                    <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-delivery-attempts>5</max-delivery-attempts>
                        <max-size-bytes>10485760</max-size-bytes>
                        <page-size-bytes>2097152</page-size-bytes>
                        <address-full-policy>PAGE</address-full-policy>
                        <message-counter-history-day-limit>10</message-counter-history-day-limit>
                    </address-setting>
                    <address-setting match="jms.queue.testQueue">
                        <dead-letter-address>jms.queue.DLQ</dead-letter-address>
                        <expiry-address>jms.queue.ExpiryQueue</expiry-address>
                        <redelivery-delay>0</redelivery-delay>
                        <max-size-bytes>10485760</max-size-bytes>
                        <page-size-bytes>2097152</page-size-bytes>
                        <address-full-policy>PAGE</address-full-policy>
                        <message-counter-history-day-limit>10</message-counter-history-day-limit>
                    </address-setting>
                </address-settings>
It is expected that the setting for jms.queue.testQueue would inherit max-delivery-attempts from default address setting "#" but it does not. Instead if uses the default value for max-delivery-attempts which is 9.

Comment 2 Miroslav Novak 2014-06-16 10:39:48 UTC
Setting as verified. Thanks Jeff!


Note You need to log in before you can comment on or make changes to this bug.