DB2 - Problembeschreibung
Problem IC62841 | Status: Geschlossen |
TRAP RESILIENCE CODE CAUSE DEADLATCH BETWEEN SNAPSHOT AND XA COMMIMT/ROLLBACK | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
Deadlatch is observed during test, a monitor thread holds the masterAppLatch (stabilizing application list), and as it iterates through all apps, it will acquire/release the transEntryLatch for each application in order to dump a stable picture of the locks held by the app; meanwhile, another thread doing XA commit processing is holding the latches in reverse order -- it's holding the transEntrylatch because it hasn't committed, and it can't commit until it updates the application status, for which it needs the master app latch. The XA thread, tries to update the application status in sqlrr_end_tran_after_DPS() ( trap resilience's code ), so this is a new deadlatch scenario. | |
Problem-Zusammenfassung: | |
Problem Description: TRAP RESILIENCE CODE CAUSE DEADLATCH BETWEEN SNAPSHOT AND XA COMMIMT/ROLLBACK Problem Summary: Deadlatch is observed during test, a monitor thread holds the masterAppLatch (stabilizing application list), and as it iterates through all apps, it will acquire/release the transEntryLatch for each application in order to dump a stable picture of the locks held by the app; meanwhile, another thread doing XA commit processing is holding the latches in reverse order -- it's holding the transEntrylatch because it hasn't committed, and it can't commit until it updates the application status, for which it needs the master app latch. The XA thread, tries to update the application status in sqlrr_end_tran_after_DPS() ( trap resilience's code ), so this is a new deadlatch scenario. | |
Local-Fix: | |
n/a | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Lösung | |
Problem is first fixed in Version 9.7 Fix Pack 1 | |
Workaround | |
n/a | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 31.08.2009 21.12.2009 21.12.2009 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP1 | |
Problem behoben lt. FixList in der Version | |
9.7.0.1 |