That sounds like a bug. My understanding of how sessions work is if you have set the AcknowledgementMode.Transactional, none of the messages that you send to producers created on that session will be visible to any consumers until the Commit() function is called. At that point, all messages sent up to that point will now become visible -- an all or nothing proposition. If this is not working correctly, can you provide some sample code showing the problem?
Thanks, Jim On Tue, Feb 3, 2009 at 8:56 AM, Bryan Murphy <bmurphy1...@gmail.com> wrote: > Essentially two phase commit. We keep running into the problem where > our message are handled before the producer can commit it's > transaction to the database, therefore the consumer does not see the > correct data. We currently work around this by either putting a sleep > delay at the beginning of the consumer (bad), or by sending the > messages after the transaction commit (lots of extra buggy code), > neither of which am I particularly happy with as a long term solution. > > Bryan > > On Thu, Jan 29, 2009 at 11:00 AM, Jim Gomes <e.se...@gmail.com> wrote: > > Hi Bryan, > > > > I'm not sure what you mean by participating inside a transaction. Are > you > > talking about implementing a two-phase commit extended transaction > > operation? Or are you talking about using the transaction acknowledgment > > mode that is part of NMS? > > > > - Jim > > > > On Mon, Dec 29, 2008 at 3:02 PM, Bryan Murphy <bmurphy1...@gmail.com> > wrote: > > > >> Is there a way I can have the sending of messages to a message queue > >> participate inside a transaction while using C# and NMS? > >> > >> Thanks, > >> Bryan > >> > > >
