To be more specific, you're not doing anything with a unit of work in an IMessageModule?
On Fri, Nov 2, 2012 at 10:00 AM, Daventry <[email protected]> wrote: > No, the transaction suppression is the first line of code in our consumer. > > > On Friday, November 2, 2012 3:36:39 PM UTC, Corey wrote: > >> DTC will kick in regardless due to Rhino.Queues participating in the >> distributed transaction. We're using almost the identical setup you >> describe minus the transaction supress and we have never seen this type of >> problem. I would look there first. Is it possible a connection to the >> database is opened prior to supressing the transaction? >> >> On Fri, Nov 2, 2012 at 9:31 AM, Daventry <[email protected]> wrote: >> >>> Hi Corey, >>> >>> I think I replied just to you instead of posting to the group. >>> >>> We're using Rhino Queues as transport. RSB version is 2.3.4.0 >>> >>> We're also supressing the TransactionScope because otherwise the DTC >>> kicks in every time we open a second connection to a DB (which is SQL >>> Server 2008 R2). I thought this was a SQL Server 2005 bug and should not >>> happen in the 2008 version... >>> >>> Thanks. >>> >>> On Friday, November 2, 2012 3:08:16 PM UTC, Corey wrote: >>> >>>> The TransactionScope timeout would be much sooner than 10 minutes. I'm >>>> not sure why you would be seeing this behavior. Which transport is being >>>> used? >>>> >>>> On Wed, Oct 31, 2012 at 11:22 AM, Daventry <[email protected]>wrote: >>>> >>>>> Hi, >>>>> >>>>> We've noticed that when our message is being processed, after 10 >>>>> minutes the message is processed even though the first run hasn't errored. >>>>> So they both run in parallel (because we have set the bus threadcount to >>>>> 5). >>>>> If the first run finishes in less than 10 minutes, then we don't see >>>>> such behavior. >>>>> >>>>> We don't have this problem when threadcount is set to 1. >>>>> >>>>> Regards. >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Rhino Tools Dev" group. >>>>> To view this discussion on the web visit https://groups.google.com/d/* >>>>> *ms**g/rhino-tools-dev/-/**VvCvUP1WXI**8J<https://groups.google.com/d/msg/rhino-tools-dev/-/VvCvUP1WXI8J> >>>>> . >>>>> To post to this group, send email to rhino-t...@googlegroups.**com. >>>>> To unsubscribe from this group, send email to rhino-tools-d...@** >>>>> googlegroups.**com. >>>>> >>>>> For more options, visit this group at http://groups.google.com/**group >>>>> **/rhino-tools-dev?hl=en<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 view this discussion on the web visit https://groups.google.com/d/** >>> msg/rhino-tools-dev/-/**nn1PmHy5Ir0J<https://groups.google.com/d/msg/rhino-tools-dev/-/nn1PmHy5Ir0J>. >>> >>> >>> To post to this group, send email to rhino-t...@googlegroups.**com. >>> To unsubscribe from this group, send email to rhino-tools-d...@** >>> googlegroups.com. >>> For more options, visit this group at http://groups.google.com/** >>> group/rhino-tools-dev?hl=en<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 view this discussion on the web visit > https://groups.google.com/d/msg/rhino-tools-dev/-/qWwyRPUyj8cJ. > > 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. > -- 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.
