|
Problem IC85483
|
Status: Closed |
DB2 CONNECTION SOCKETS MAY BE INHERITED BY NEW PROCESSES |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
In Windows a socket handle created by the WSASocket or the
socket function is inheritable by default. Similarly, sockets
created on UNIX are not automatically marked "close-on-exec".
This means that sockets created by an application will be
inherited by child processes by default. This behavior can lead
to a variety of unexpected and undesirable behaviors when those
sockets
are related to DB2 database connections.
When a DB2 application that is connected to a database starts a
new
child program, those database connections are not intended to be
available
to the child. New programs should establish their own database
connections
if required.
This fix prevents DB2 connection sockets from being inherited by
new programs.
Specifically, they will not be inherited across CreateProcess
calls on Windows and
they are marked "close-on-exec" on UNIX and Linux. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Windows & Linux *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to v10.1 Fixpack 1 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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 v10.1 Fixpack 1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 24.07.2012
05.11.2012
05.11.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
