Re: Constant Message Redelivery Problem

Question

You can get redelivery for other reasons as well. Redelivery occurs if the message is
          participating in a transaction, and the transaction fails for any reason.
          For example, if the MDB in turn calls an EJB which in
          turn calls JDBC then the tx becomes two-phase. If the JDBC call fails then the tx
          will roll back. Or if the tx times-out: the default tx timeout is 30 seconds, so if
          the MDB takes longer than 30 seconds then the tx will roll-back and message the will
          get redelivered.
          Even if the tx succeeds, in some cases you may have error states that re-enqueue the
          received message but let the transaction commit (WLI, BEA's integration product, can do
          this).
          This looks like the redelivery of a failed message, but is actually the delivery of a new
          version.
          Duplicates occur if a Queue MDB's descriptor actually points at a topic destination.
          Check for this one by comparing the JNDI name in config.xml against the
          descriptor destination type field...
          Tom
          sunshine wrote:
          > I encountered the same problem of repeat message delivery. In our situation, we are
          > using JMS JDBC Store and when the database goes down and comes back up, the MDB starts
          > processing messages but the messages keep recycling in the JMS Store.
          >
          > The MDB code tried catching all possible exceptions like RuntimeException and Exception.
          > None of these exceptions are logged. When we re-start the WL managed servers, those
          > messages in the JMS Store were flushed off.
          >
          > Any idea what caused the repeat message redelivery?? Thanks.
          >
          > Tom Barnes <[email protected]> wrote:
          > >Your MDB may be throwing a RuntimeException, which forces message
          > >redelivery. Put a try/catch/Throwable in the outermost scope of your
          > >onMessage() code to see if this is case.
          > >
          > >Note that in 6.1 and up you can configure redelivery delays, max redelivery
          > >counts and error destinations to alleviate this problem...
          > >
          > >Tom
          > >
          > >Toad wrote:
          > >
          > >> I have a message-driven bean listening on a message queue and everything
          > >> appears to work the first time the message is sent. The message is processed
          > >> and the OnMessage method returns without incident. There are no errors
          > >and
          > >> no exceptions are thrown by the JMS client or in the MDB itself. PROBLEM:
          > >> Message continually redelivered pegging the CPU at 100%. Inspection of
          > >the
          > >> JMSSTORE and JMSSTATE reveals messages still queued. Any ideas?
          > >
          

Answer 1

And make sure that your MDB is not throwing Errors or RuntimeExceptions,
          as these don't necessarily get logged, but they cause rollbacks.
          Put a "try {} catch (RuntimeException re)
          { log; throw re; } catch (Error er) { log; throw er; }"
          around all the code within the MDB's "onMessage()" callback
          to see if this is happening.
          Manikyala Peddi wrote:
          > Hi,
          >
          > I have a MDB which is calling an EJB. The redelivery override period was set at 60 sec.
          >
          > Before completing the first message the same message is redelivered.The processing time in onMessage in MDB takes more than the Redelivery Override Period. Is there a way to prevent the delivery of the duplicate message before completing the first message.Iam using Weblogic 7.1
          >
          > Thanks
          >
          > Manikyala