> > 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 ? thanks, Farhat. =========================================================================== 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".
- Re: EJB 2.0 spec: Association of a message-driven b... Cedric Beust
- Re: EJB 2.0 spec: Association of a message-driven b... Evan Ireland
- Re: EJB 2.0 spec: Association of a message-driven b... Cedric Beust
- Re: EJB 2.0 spec: Association of a message-driven b... Gene Chuang
- Re: EJB 2.0 spec: Association of a message-driven b... Richard Monson-Haefel
- Re: EJB 2.0 spec: Association of a message-driven b... Evan Ireland
- Re: EJB 2.0 spec: Association of a message-driven b... Cedric Beust
- Re: EJB 2.0 spec: Association of a message-dri... Richard Monson-Haefel
- Re: EJB 2.0 spec: Association of a message-driven b... Cedric Beust
- Re: EJB 2.0 spec: Association of a message-dri... Evan Ireland
- Re: EJB 2.0 spec: Association of a message-driven b... Muhammad Farhat Kaleem
- Re: EJB 2.0 spec: Association of a message-dri... Evan Ireland
