Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
middleburgredneck
Starting Member
2 Posts |
Posted - 2010-08-06 : 16:18:06
|
recently we have this new issue where the service broker will requeue the message exactly at the 10 minute mark and because we have a multithreaded environment this is getting picked up again by a second thread.does anyone know what changed recently or patches may have caused this requeue at the 10 minute mark? |
|
middleburgredneck
Starting Member
2 Posts |
Posted - 2010-08-08 : 11:50:49
|
quote: Originally posted by middleburgredneck recently we have this new issue where the service broker will requeue the message exactly at the 10 minute mark and because we have a multithreaded environment this is getting picked up again by a second thread.does anyone know what changed recently or patches may have caused this requeue at the 10 minute mark?
OK, we resolved this issue. apparently the .net 4.0 framework doesn't allow you to set your transactionscope timeouts in the code as we have done in the past. we had to make the machine.config changes by adding<system.transactions> <machineSettings maxTimeout="02:00:00"/> <defaultSettings timeout="02:00:00"/> </system.transactions>to the machine.config file. using the 2.0 framework we did not have to make these entries as our code was overriding teh default value to begin with. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
|
|