|
Problem IT16930
|
Status: Closed |
MSDTC PROCESS CAN CRASH IN DB2APP64.DLL
|
| product: |
DB2 CONNECT / DB2CONNCT / A50 - DB2 |
| Problem description: |
The MSDTC (Microsoft Distributed Transaction Coordinator)
process (msdtc.exe) can crash producing a call stack as follows:
STACK_TEXT:
db2app64!sqleInitApplicationEnvironment+0x68a
[K:db2_v105fp7
tx64s151221engnsqesqleapie.C @ 838]
db2app64!sqleUCcheckProcessInit+0x5e
[K:db2_v105fp7
tx64s151221engnsqeusqleu_client.C @ 7940]
db2app64!sqleuApplicationInit+0x1f
[K:db2_v105fp7
tx64s151221engnsqeusqleu_client.C @ 7983]
db2app64!sqlxa_open+0x104
[K:db2_v105fp7
tx64s151221engnsqxasqlxapi.C @ 2617]
msdtctm!CValidateTask::TaskRoutine+0xa8
msdtctm!CTaskManager::ValidateThreadRoutine+0xb9
kernel32!BaseThreadInitThunk+0xd
ntdll!RtlUserThreadStart+0x1d
The underlying cause is a Windows Thread Local Storage index
leak. When a thread terminates inside the MSDTC process via
the DB2 client driver, it fails to free a TLS slot. This leads
to a situation where we have exhausted all TLS slots. When that
happens a new thread cannot be allocated properly and we crash
in our driver.
This is similar to APAR# IC84308 but ultimately a new issue
leading to a similar crash. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 10.5 Fix Pack 9 or higher *
**************************************************************** |
| Local Fix: |
n/a |
| Solution |
|
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner :
follow-up : IT21791 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 06.09.2016
29.09.2017
29.09.2017 |
| Problem solved at the following versions (IBM BugInfos) |
9.0.
|
| Problem solved according to the fixlist(s) of the following version(s) |
