Fix (APAR):  PK61753

Status:  Fix

Release:  6.1.0.9,6.1.0.13,6.1.0.11

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

Supersedes Fixes:  

CMVC Defect:  PK61753

Byte size of APAR:  30993

Date: 2008-03-28

Abstract:  Virtual Member Manager will throw a ServiceUnavailableExcepiton if there is connection problem to LDAP.

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

ERROR DESCRIPTION:                                              
IBM WebSphere Application Server is configured to use a load    
balancer/proxy sitting in front of LDAP servers.  It uses       
Federated repository. It takes few attempts to login to the     
administrative console.                                         
                                                                
The error that we see in the log is:                            
                                                                
com.ibm.ws.wim.adapter.ldap.LdapConnection getRangeAttributes   
CWWIM4520E The 'javax.naming.ServiceUnavailableException:       
xx.xxxxx.com:3268; socket closed;                               
remaining name 'CN=xxxxxxx,OU=Generics,OU=xxxxx                 
Users,dc=xxxxx,dc=com'                                          
resolved object com.sun.jndi.ldap.                              
LdapCtx@7b907b90' naming exception occurred during processing.  
                                                                
The Application Server is in one location the current LDAP      
proxy resides in another location.                              
We tested the scenario without the proxy locally as well as     
as in the other location and it works fine, the issue is only   
when we connect to LDAP using the proxy.                        

LOCAL FIX:                                                      
N/A                                                             

PROBLEM SUMMARY

USERS AFFECTED:
This affects IBM Websphere Application
Server V6.1 users who use federated
repositories (VMM - virtual member manager).

PROBLEM DESCRIPTION:
Virtual Member Manager will throw a
ServiceUnavailableExcepiton if there
is connection problem to LDAP.

RECOMMENDATION:
None

If there is network problem connecting to LDAP, the following
exception will be thrown and the connection to LDAP will not
be retried:

[12/5/07 12:35:51:749 CST]  0000000a exception     E
com.ibm.ws.wim.adapter.ldap.LdapConnection getDirContext
com.ibm.websphere.wim.exception.WIMSystemException:
CWWIM4520E The 'javax.naming.ServiceUnavailableException:
server1.com:26362; socket closed' naming exception occurred
during processing.
at com.ibm.ws.wim.adapter.ldap.LdapConnection
.getDirContext(LdapConnection.java:1355)
at com.ibm.ws.wim.adapter.ldap.LdapConnection
.search(LdapConnection.java:2378)

PROBLEM CONCLUSION:                                             
The problem has been fixed.  The exception will not be thrown   
and the connection to LDAP can be retried.                      
                                                                
This fix is included in PK61753 and targeted for fix pack       
6.1.0.17.                                                       
Please refer to the recommended updates page for delivery       
information:                                                    
http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg27004980 


Directions to apply fix:  
Fix applies to Editions:
Release 6.1
x_ Application Server (Express or BASE)
x_ Network Deployment (ND)
__ WebSphere Business Integration Server Foundation (WBISF)
__ Edge Components
__ Developer
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.1.0.13 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.1.0.0-WS-WAS-IFPK61753.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.1.0.0-WS-WAS-IFPK61753.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.1.0.0-WS-WAS-IFPK61753.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: