Fix (APAR):  PM51069

Status:  Fix

Release:  7.0

Operating System:  HPUX

Supersedes Fixes:  

CMVC Defect:  PM51069


Abstract: WAS SDK APAR to deliver ifix for JDK APAR IV09082 

ERROR DESCRIPTION:                                             
Error Message: java.net.SocketException: Invalid  
argument(errno:22)  
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)  
at  
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.jav  
a:567)  
at ...  
.  
Stack Trace: The problem is only in HP 64 bit  
Itanium(IA64)builds  

LOCAL FIX:
This problem was released with the HP JDK/JRE version 1.6.0.10.  
The 64-bit libnio.so library available from one of the  
immediately prior levels of the HP JDK/JRE could be  
used to substitute for the same library of the 1.6.0.10  
release (or those following presenting the issue, up to the  
fixed release).

PROBLEM SUMMARY:
java.net.SocketException: Invalid argument(errno:22). The  
problem is specific to HP 64 bit Itanium(IA64) builds.   


USERS AFFECTED:
IBM WebSphere Application Server Version 7.0 users

PROBLEM DESCRIPTION:
java.net.SocketException: Invalid  
argument(errno:22)

RECOMMENDATION:
Apply this apar to upgrade your SDK to SDK6 SR9-FP1 plus this fix.

PROBLEM CONCLUSION:                                            
Applying this fix will upgrade your SDK to SDK6 SR9-FP1 plus this fix.


Directions to apply fix:  
Use the latest Update Installer to install this Apar:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

Fix applies to Editions:
IBM WebSphere Application Server V7.0.0.x
_x_ Application Server (Express or BASE)
_x_ Network Deployment (ND)
___ WebSphere Business Integration Server Foundation (WBISF)
___ Edge Components
___ Developer
___ 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.
* Use the latest 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 .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 (.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 (.pak file name).

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: