Probably because it means that you don't provide your own local tx. On Fri, Apr 16, 2010 at 1:50 PM, Sebastien Crocquesel <[email protected]>wrote:
> I goes into the same problem when connecting to a mysql database. > I assume it was the problem of the database and as such I prefer to use a > new TransactionScope(TransactionScopeOption.Suppress)). > I only have to make a single select statement so no big deal and the > handler interact with an other DTC compliant database so i can't disable it > globally. > I don't know if NHibernate for example could handle this when opening a > session or flushing or if there is a connection string argument that can > tell to do so by the sql provider itself. > > > Aside, i'm wondering why a > Receive/Send(MessageQueueTransactionType.None) would enlist in the > transaction scope promoting it to a distributed transaction ? > > > 2010/4/12 philip <[email protected]> > > Ok pushed patch, it is now configurable through the Bus configuration >> attribute consumeInTransaction whose default value is set to true. >> >> On Apr 12, 10:11 am, Ayende Rahien <[email protected]> wrote: >> > Philip, >> > Yes, that is intentional and desirable. >> > You can patch it so you can patch it so a transaction will not be >> started >> > based on some config option, but even if the queue is non transactional, >> a >> > DTC is still important in many scenarios. >> > >> > >> > >> > On Mon, Apr 12, 2010 at 11:48 AM, philip <[email protected]> >> wrote: >> > > The MsmqTransport class automatically begins a transaction scope in >> > > the ReceiveMessageInTransaction method regardless of whether the >> > > underlying queue is transactional or not. Is this correct? >> > >> > > This is a problem for us as our consumers interact with a sql database >> > > which is not configured to support DTC, can I patch it such that a >> > > TransactionScope is only created if the underlying queue is >> > > transactional? >> > >> > > -- >> > > You received this message because you are subscribed to the Google >> Groups >> > > "Rhino Tools Dev" group. >> > > To post to this group, send email to [email protected] >> . >> > > To unsubscribe from this group, send email to >> > > [email protected]<rhino-tools-dev%[email protected]> >> <rhino-tools-dev%2Bunsubscribe@ googlegroups.com> >> > > . >> > > For more options, visit this group at >> > >http://groups.google.com/group/rhino-tools-dev?hl=en. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Rhino Tools Dev" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<rhino-tools-dev%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/rhino-tools-dev?hl=en. >> >> > -- > You received this message because you are subscribed to the Google Groups > "Rhino Tools Dev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<rhino-tools-dev%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/rhino-tools-dev?hl=en. > -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
