A fix is available
APAR status
Closed as program error.
Error description
A Multithreaded application (using sockets in it's code) when killed can leave some sockets still open. These sockets remain in LISTEN state. These sockets may be holding on to a particular port and so these ports will not available for any application. So if any application is dependent on a particular port number to restart, will not restart. This problem was investigated and found in aix with oracle oacore & oafm applications when using java 1.6. Example:- one can see following socket state even after the using process exited. # netstat -Aan | grep 21552 f10002000004e398 tcp4 0 0 *.21552 *.* LISTEN
Local fix
The user can check using # netstat -Ana | grep <port number> This will give the port that is still in the listen state. use rmsock to remove these sockets Or # export XPG_SUS_ENV=ON
Problem summary
Fileptr mishandling during dup2
Problem conclusion
Handle interrupts return code from closex
Temporary fix
Comments
5300-08 - use AIX APAR IZ69627 5300-09 - use AIX APAR IZ69419 5300-10 - use AIX APAR IZ63084 5300-11 - use AIX APAR IZ65101 6100-04 - use AIX APAR IZ64468
APAR Information
APAR number
IZ65101
Reported component name
AIX 5.3
Reported component ID
5765G0300
Reported release
530
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Submitted date
2009-11-12
Closed date
2009-11-12
Last modified date
2013-04-11
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
AIX 5.3
Fixed component ID
5765G0300
Applicable component levels
R530 PSY U832725
UP10/02/08 I 1000
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG11P","label":"APARs - AIX 5.3 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"530","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
11 April 2013