glassfish
  1. glassfish
  2. GLASSFISH-6617

Ignoring MDB's activation-spec for RedeliveryInterval and RedeliveryAttempts

    Details

    • Issuezilla Id:
      6,617

      Description

      I set these parameters using activation-config within sun specific descriptor.
      It's ignored in runtime.

      Futhermore, documentation contains information that these parameters affect on
      container's behaviour in case of throw RuntimeException from onMessage method.
      What about MessageDrivenContext.setRollbackOnly() method's invoke ? Does
      container should treat it in another way?

      I tried both ways, and found:
      1) in case of using setRollbackOnly() - message is redelivered with no limit
      2) in case of throwing RuntimeException - message is redelivered once, and dump
      to the default dead-message-queue

      regards
      Beniamin

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            David Zhao
            Reporter:
            beniamin
          • Votes:
            3 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: