This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I am randomly receiving timeouts on transactions that use the TransactionScope. But if I simply push the save button again the save works correctly. I have checked the SQL Server (SQL Server 2008R2), and it is using virtually no resources, and there is no noticeable spike what I run any transactions. I have checked CPU, memory, network and disk performance indicators and all are normal. The network is a Gigabit network with only about 20 desktops, so again no bottleneck there. The timeouts happen a couple of times a day, and completely random times, and each time if the transaction is repeated all works as planned. The app is using .Net Framework 4 on Windows 7 on i5 and i7 processor systems. I am still using the 3.11 release of Lightspeed. There is no noticable pattern to the methods that fail, all over the place. Can anyone give me any idea how I can pin down this cause so I can get rid of this anoyance.
|
|
|
|
|
I would do a bit of profiling to check that you are not running in to a blocking issue at the database which is causing it to hang causing the timeout. This is a good article on how to diagnose if its a blocking related issue: http://support.microsoft.com/kb/224453 Is it isolated to a specific action in the system or does this happen pretty much randomly across the system irrespective of load or other external factors? It is always helpful to pin down any common factors that lead to the problem as they will give you something to work with in terms of tracking down the cause(s).
Jeremy |
|
|
|
