Details

    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Rejected
    • Affects Version/s: JBossAS-4.2.0.GA
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Some JMS providers e.g. JBoss Messaging implement an optional redelivery delay between successive deliveries of the same message after rollbacks due to a failure.

      This is a nice feature and is designed to prevent thrashing which can consume CPU when failure in delivery occurs frequently.

      When using such providers with JBoss AS MDBs, using either the JMSContainerIvoker or JCA 1.5 inflow, this fetaure is unusable since the MDB container wraps the onMessage method of the MDB and catches any exceptions thrown by the MDB and handles redlivery itself.

      Consequently the provider does not have a chance to execute any redelivery delay logic.

      It would be great for the MDB container to implement redelivery delay itself.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                timfox Tim Fox
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: