Thank you for your reply.
"Read Uncommitted" was the equivalent of a typo; I accidentally modified that action while trying to "beautify" the taf (with labels that are easier to understand then those used in my actual testfile). Sorry for the confusion. I can confirm that the deadlock occurs with the "Read/Write Exclusive". And it always happens in the sections labeled 2__ (most often) and 3__. This is actually the problem: section 2 takes most time to complete, and if the section is not actually protected, it is most likely to get into a deadlock. If there is nothing else wrong with my code, I believe this looks like a serious problem. Mihai. -----Original Message----- From: witango man [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 02, 2004 17:27 To: [EMAIL PROTECTED] Subject: Re: Witango-Talk: BeginTransaction - EndTransaction section: does it really work? Why is the first transaction "Read Uncommitted"? Read uncommitted reads rows that have been changed by other database users in a transaction, but for which the transaction has not been committed or rolled back. Is this what you intended and if you change that first Begin Transaction to Exclusive do you still get the same problem... --- [EMAIL PROTECTED] wrote: > Hi everybody, > > While checking the timing needed for different database operations I > noticed that repeatedly pressing (very fast) the reload button on my > browser would generate a deadlock error (see below). > How is this possible? Each database access is included into a > BeginTransaction - EndTransaction section. > I could not reproduce this problem for small and simple databases, > like the Nortwind or Pubs DBs that come along with the MS-SQL. > Still the problem is troublesome, because my DB is fairly complex and > I depend on BT-ET to provide unique access to the DB and protect > against multi-access while doing critical operations. > > I have included the code, which is very simple, if somebody would be > curious enough and had the inclination to find the problem. > My configuration: Windows 2000 pro, MS-SQL 2000, Apache 2, Witango > Server; all updated. > > Is anybody else getting the same problem? > > Many thanks for any suggestions you may have. > Mihai Olariu > > PS: > A solution to this problem is to include my own semaphores around the > BT-ET sections. This, I verified, solves the problem indeed. But this > would be like wearing belt and suspenders on the same pair of > trousers. Gosh, I hope I am wrong... > > > Error > > An error occurred while processing your request: > > File: dbTest1.taf > Position: get_latest_userID > Class: DBMS > Main Error Number: 1205 > > > [Microsoft][ODBC SQL Server Driver][SQL > Server]Transaction (Process ID 60) > was deadlocked on {lock} resources with another > process and has been chosen > as the deadlock victim. Rerun the transaction. > 40001 > > File: dbTest1.taf > Position: get_latest_userID > Class: Internal > Main Error Number: -101 > > > General error during data source operation. > > > File: dbTest1.taf > Position: get_latest_userID > Class: Internal > Main Error Number: -101 > > > General error during data source operation. > > > ATTACHMENT part 2 application/octet-stream name=DBtest1.zip > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to > http://www.witango.com/developer/maillist.taf > __________________________________ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/ ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
