Muhammad Farhat Kaleem wrote:
>
> >
> > No. JMS shouldn't deliver the same message twice (or at least if
> > a message is delivered twice in unusual circumstances the JMSRedelivered
> > flag should be correctly set).
> >
>
> In case of a container-managed Tx rollback, the message would be put back on
> the destination, and then redelivered to the consumer, which could be the
> same MDB. Should the message have the redelivered flag set to true the
> second time around, or should it be false, since it is a new Tx in any case
> ? How do different vendors see this scenario ?
Our interpretation is that redelivery in a separate transaction context still
requires the setting of the JMSRedelivered flag. I would expect that the
other vendors and implementors will agree.
________________________________________________________________________________
Evan Ireland Sybase EAServer Engineering [EMAIL PROTECTED]
Wellington, New Zealand +64 4 934-5856
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
