|
Problem IC91777
|
Status: Closed |
.NET APPLICATION MAY HANG AFTER RECEIVING COMMUNICATION ERROR |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
.NET application may hang after receiving communication error.
In trace you can see even after connection failure, DB2 calls
being executed which will result in hang situation like this:
1125836 | | | | | | DB2DataReader.Dispose entry
1125837 | | | | | | | DB2DataReader.Dispose entry
1125838 | | | | | | | DB2DataReader.Dispose data [probe 15]
1125839 | | | | | | | | SQLFreeStmt entry
1125840 | | | | | | | | | sqloxltc_app entry
1125841 | | | | | | | | | | sqlo_xlatch::getConflict entry
SQLFreeStmt is being called but never exited. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V10.1 FP3 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 V10.1 FP3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.04.2013
01.10.2013
01.10.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
