Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-20077

max-redelivery-delay initialization

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 34.0.1.Final
    • JMS
    • None
    • Hide

      C.f. settings in description.

      Show
      C.f. settings in description.
    • Hide

      Add max-redelivery-delay property to address-setting

      Show
      Add max-redelivery-delay property to address-setting
    • ---
    • ---

      Updated from wildfy 19 (artemis version 2.10.1) to 34 (artemis version 2.37.0).

      The setting in my standalone.xml was:

      <address-setting name="jms.queue.TestQueue" redelivery-delay="600000" ....>

      I needed to change it to:

      <address-setting name="jms.queue.TestQueue" redelivery-delay="600000" max-redelivery-delay="600000"....

      I think if the parameter max-redelivery-delay is not there it should fall back to redelivery-delay (in my case 600000) as an initialization parameter and not to 0.

      Someone from the artemis mailing list referred to this:

      Hi Robert,
the code related to the redelivery-delay is the same in Apache ActiveMQ
Artemis 2.10.1 and 2.37.0 versions. This issue could be caused
by WFLY-19072[1], it sets the MaxRedeliveryDelay default value on the root
of AddressSettings to 0, see
https://github.com/wildfly/wildfly/commit/adf1c4eb41e1ebd69119fea9305ebfeba13ecf1a#diff-c841daa7f5b238a2987f4993f03c20610b65ac7dfb4b4382eea83663af40a079R79
[1] https://issues.redhat.com/browse/WFLY-19072
Regards,
Domenico

      Source

      Documentation

              mpetrov@redhat.com Michal Petrov
              murphy99_jira Robert Palm (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: