Uploaded image for project: 'Application Server 3 4 5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-7465

Some issues with JCA's DLQ handling

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • None
    • None
    • JCA service
    • None

    Description

      1. JCA ignores the DLQ attribute specified in the queue's configuration file.
      2. JCA doesn't correctly handle the max redelivery limit. If the limit is set to n, it doesn't send the message to DLQ until n+1 th redelivery.
      3. JCA doesn't correctly handle its relation with JBM's max re-delivery control. Problems will show if you specify the DLQMaxResent count to be greater than JBM's default (10), in which case JBM will send the message to DLQ always at 10th re-delivery, giving JCA no chance to control.

      Attachments

        Issue Links

          is related to

          Feature Request - Feature requests from customers and/or users JBAS-7601 Change the defaults to useDLQ=false for JBoss Messaging

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-3352 Change the defaults to useDLQ=false for JBoss Messaging

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-5537 Change the defaults to useDLQ=false for JBoss Messaging

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              jpederse@redhat.com Jesper Pedersen
              gaohoward Howard Gao
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: