Why is my transactional application experiencing what appears to be an inordinately high number of deadlocks?
There are a few potential common explanations for this kind of behavior: • The application may be acquiring database objects in inconsistent orders; having threads of control always acquire objects in the same order will reduce the frequency of deadlocks. • If you frequently read a piece of data, modify it and then write it, you may be inadvertently causing a large number of deadlocks. Try specifying the DB_RMW flag on your {{DB->get()}}} calls. • Finally, reducing the isolation level can significantly reduce the number of deadlocks seen by the application. See the Isolation and Degrees of isolation sections of the Berkeley DB Reference Guide for more information.
Related Questions
- I have noticed that the percentage appears to be rather high when I run the CASPER Provider report entitled Error Summary by Facility report. How is this report calculated?
- When my docking dialog is docked to the bottom of my MDI application the status bar appears to be above. What is going on?
- What is the Australian High Commission application fee? Is it refundable?
