Fixes are available
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
Obtain the fix for this APAR.
APAR status
Closed as program error.
Error description
Performance issues when using federated repositories with RACF registry When starting Websphere Application Server using federated repositories, the server takes a long time to start up, if it's configured to use the RACF registry. It especially takes long if there are lots of users in the RACF registry. You may notice the below exception during the server startup which may prevent the server to start. com.ibm.websphere.wim.exception.WIMApplicationException: CWWIM4506E Virtual member manager failed to search the entity : 'java.lang.NullPointerException'. at com.ibm.ws.wim.adapter.urbridge.URBridge.search(URBridge.ja at com.ibm.ws.wim.ProfileManager.searchRepository(ProfileManag at com.ibm.ws.wim.ProfileManager.searchImpl(ProfileManager.jav at com.ibm.ws.wim.ProfileManager.genericProfileManagerMethod(P at com.ibm.ws.wim.ProfileManager.search(ProfileManager.java:37 at com.ibm.websphere.wim.ServiceProvider.search(ServiceProvide at com.ibm.ws.wim.registry.util.UniqueIdBridge.getUniqueUserId at com.ibm.ws.wim.registry.WIMUserRegistry$6.run(WIMUserRegist at com.ibm.ws.wim.security.authz.jacc.JACCSecurityManager.runA at com.ibm.ws.wim.security.authz.ProfileSecurityManager.runAsS at com.ibm.ws.wim.registry.WIMUserRegistry.getUniqueUserId(WIM at com.ibm.ws.security.registry.UserRegistryImpl.createCredent at com.ibm.ws.security.ltpa.LTPAServerObject.authenticate(LTPA at com.ibm.ws.security.server.lm.ltpaLoginModule.login(ltpaLog at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcc at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingM at java.lang.reflect.Method.invoke(Method.java:618) at javax.security.auth.login.LoginContext.invoke(LoginContext. at javax.security.auth.login.LoginContext.access$000(LoginCont at javax.security.auth.login.LoginContext$4.run(LoginContext.j at java.security.AccessController.doPrivileged(AccessControlle at javax.security.auth.login.LoginContext.invokePriv(LoginCont at javax.security.auth.login.LoginContext.login(LoginContext.j at com.ibm.ws.security.auth.JaasLoginHelper.jaas_login(JaasLog at com.ibm.ws.security.auth.ContextManagerImpl.login(ContextMa at com.ibm.ws.security.auth.ContextManagerImpl.login(ContextMa at com.ibm.ws.security.auth.ContextManagerImpl.login(ContextMa at com.ibm.ws.security.auth.ContextManagerImpl.getServerSubjec at com.ibm.ws.security.auth.ContextManagerImpl.getServerSubjec at com.ibm.ws.security.auth.ContextManagerImpl.initialize(Cont at com.ibm.ws.security.auth.ContextManagerImpl.initialize(Cont at com.ibm.ws.security.core.SecurityContext.enable(SecurityCon at com.ibm.ws.security.core.distSecurityComponentImpl.initiali at com.ibm.ws.security.core.distSecurityComponentImpl.startSec at com.ibm.ws.security.core.SecurityComponentImpl.startSecurit at com.ibm.ws.security.core.ServerSecurityComponentImpl.start( at com.ibm.ws.runtime.component.ContainerImpl.startComponents( at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerI at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.ja at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServe at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:140 at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:461) at com.ibm.ws.runtime.WsServer.main(WsServer.java:59)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: NullPointerException and performance * * issues are seen during server startup * * while using Federated repositories * * with RACF. * **************************************************************** * RECOMMENDATION: * **************************************************************** NullPointerException and performance issues are seen during server startup while using Federated repositories with RACF.When starting Websphere Application Server using federated repositories, the server takes a long time to start up, if it's configured to use the RACF registry. It especially takes long if there are lots of users in the RACF registry. You may notice the below exception during the server startup which may prevent the server to start. The Exception thrown as:- com.ibm.websphere.wim.exception.WIMApplicationException: CWWIM4506E Virtual member manager failed to search the entity : 'java.lang.NullPointerException'.
Problem conclusion
Code changes made to correct the NullPointerException as well to use the correct API for user validation during login, which fixes performance issue in server startup. APAR PM11190 is currently targeted for inclusion in Service Level (Fix Pack) 6.1.0.33 of WebSphere Application Server V6.1. Please refer to URL: //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack availability.
Temporary fix
Comments
APAR Information
APAR number
PM11190
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-03-30
Closed date
2010-07-14
Last modified date
2011-04-21
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
WEBSPHERE FOR Z
Fixed component ID
5655I3500
Applicable component levels
R610 PSY UK59848
UP10/09/11 P F009
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
Document Information
Modified date:
25 October 2021