Fix (APAR):  PK40415

Status:  Fix

Release:  6.0.2.19,6.0.2.17

Operating System:  AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux Red Hat - pSeries,Linux zSeries,OS/390,OS/400,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  PK40415

Byte size of APAR:  10440

Date: 2007-06-28

Abstract:  TCPC0007E audit messages appear in the SystemOut files frequently, even when the system appears to be working fine.

Description/symptom of problem:  
PK40415 resolves the following problem:

ERROR DESCRIPTION:                                              
Despite WAS continuing to run and handle traffic,  frequent     
TCPC0007E audit messages appear. One source triggering this     
behavior is clients opening and immediately closing sockets     
against the server.                                             

LOCAL FIX:                                                      
testfix                                                         

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Application Server version 6
users of the TCP channel.

PROBLEM DESCRIPTION:
TCPC0007E audit messages appear in the
SystemOut files frequently, even when
the system appears to be working fine.

RECOMMENDATION:
None

When the TCP channel performs a socket accept() call, if it
receives a null socket object, it considers that an error
condition. The first five in a row will trigger the audit
message about that port no longer accepting connections.

PROBLEM CONCLUSION:                                             
Because there was a selector listening for new accept keys, it  
was thought that the accept() would not fail except under severe
conditions. So when a null socket was returned, the audit was   
made to inform the Application Server administrator of the      
error condition (turning off the TCP network layer of the       
Operating                                                       
System will do this for example).                               
However, if a new socket is closed by the client side before    
the accept() is made, it will validly return the null socket at 
that point, despite the selector firing on the key. The code    
is changed to move the audit from the first five nulls in a row 
to be every 100th. If working traffic is accepted, then the     
error counter is started over.                                  
                                                                
This is targeted for fixpacks 6.0.2.21 and 6.1.0.9.             
Please refer to the recommended updates page for delivery       
information:                                                    
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980   


Directions to apply fix:  
Fix applies to Editions:
Release 6.0
_x_ Application Server (Express or BASE)
_x_ Network Deployment (ND)
_x_ Extended Deployment (XD)

Install Fix to:
Method:
__ Application Server Nodes
__ Deployment Manager Nodes
_x_ Both

NOTE:
The user must:
* Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* Logged in with the same authority level when unpacking a fix, fix pack or refresh pack.
* Be at V6.0.2.2 or newer of the Update Installer. This can be checked by reviewing the level of the Update Installer in file <was_root>/updateinstaller/version.txt.

The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

For detailed instructions to Extract the Update Installer see the following Technote:
http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21205400

1) Copy 6.0.2.17-WS-WAS-IFPK40415.pak file directly to the maintenance directory

2) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to.

3) Launch Update Installer

4) Enter the installation location of the WebSphere product you want to update.

5) Select the "Install maintenance package" operation.

6) Enter the file name of the maintenance package to install (6.0.2.17-WS-WAS-IFPK40415.pak file which was copied in the maintenance directory).

7) Install the maintenance package.

8) Restart WebSphere

Directions to remove fix:  
NOTE:
* The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED
* DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED
* YOU MAY REAPPLY ANY REMOVED FIX

Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied.

1) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against.

2) Start Update Installer

3) Enter the installation location of the WebSphere product you want to remove the fix.

4) Select  "Uninstall maintenance package" operation.

5) Enter the file name of the maintenance package to uninstall (6.0.2.17-WS-WAS-IFPK40415.pak).

6) UnInstall maintenance package.

7) Restart WebSphere

Directions to re-apply fix:  
1) Shutdown WebSphere.

2) Follow the Fix instructions to apply the fix.

3) Restart WebSphere.



Additional Information: