suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT34606 Status: Closed

USING CFGREFRESHINTERVAL IN A MULTI-THREADED CLI APPLICATION LEADS TO
SEGMENTATION FAULT

product:
DB2 CONNECT / DB2CONNCT / B50 - DB2
Problem description:
When parameter CfgRefreshInterval is specified in cfg file a new
thread is spawned which re-reads the db2dsdriver.cfg file for
certain supported keywords for every interval sec specified and
apply those changes for every connection handle.
When multiple threads are involved to have multiple connections
using DB2 CLI driver along with configuring parameter
CfgRefreshInterval in cfg file would lead to Exception
0xc0000005 on windows and similiar core dump or segmentation
fault can be seen in other platforms as well.

similar stack trace as shown below can be seen:
0000002c`730f5118 00007ff8`67e213ed
ntdll!NtWaitForMultipleObjects+0xa
0000002c`730f5120 00007ff8`6a518271
KERNELBASE!WaitForMultipleObjectsEx+0xe1
0000002c`730f5400 00007ff8`6a517c93
kernel32!WerpReportFaultInternal+0x581
0000002c`730f5970 00007ff8`67f0176f
kernel32!WerpReportFault+0x83
0000002c`730f59a0 00007ff8`6a90f173
KERNELBASE!UnhandledExceptionFilter+0x23f
0000002c`730f5a90 00007ff8`6a8f1dd6
ntdll!RtlUserThreadStart$filt$0+0x3e
0000002c`730f5ad0 00007ff8`6a90345d
ntdll!_C_specific_handler+0x96
0000002c`730f5b40 00007ff8`6a8c4937
ntdll!RtlpExecuteHandlerForException+0xd
0000002c`730f5b70 00007ff8`6a9025ea
ntdll!RtlDispatchException+0x197
0000002c`730f6240 00007ff8`41eef7ae
ntdll!KiUserExceptionDispatch+0x3a
0000002c`730f6800 00007ff8`420e979f
db2app64!CLI_rccGetDbParamsList+0xde
[S:db2_v115
tx64s1906101300engncliclircc.C @ 1652]
0000002c`730f6a00 00007ff8`4255b401
db2app64!CLI_cpCfgRefreshMon+0x17f
[S:db2_v115
tx64s1906101300engncliclicpool.C @ 871]
0000002c`730f6d20 00007ff8`41884f7f
db2app64!sqloAppThdEntry+0x61
[S:db2_v115
tx64s1906101300engnsqosqloathd.C @ 101]
0000002c`730ffce0 00007ff8`41885126
msvcr120_7ff841860000!_callthreadstartex+0x17
[f:ddvctoolscrtcrtw32startup	hreadex.c @ 376]
0000002c`730ffd10 00007ff8`6a4113d2
msvcr120_7ff841860000!_threadstartex+0x102
[f:ddvctoolscrtcrtw32startup	hreadex.c @ 354]
0000002c`730ffd40 00007ff8`6a8854f4
kernel32!BaseThreadInitThunk+0x22
0000002c`730ffd70 00000000`00000000
ntdll!RtlUserThreadStart+0x34
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* Db2Connect Users                                             *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.5.5.1 or higher                            *
****************************************************************
Local Fix:
avoid using CfgRefreshInterval  in such scenario
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* Db2Connect Users                                             *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.5.5.1 or higher                            *
****************************************************************
Comment
Upgrade to Db2 11.5.5.1 or higher
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.10.2020
06.04.2021
06.04.2021
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)