PQ66407: LDAP 32 ERROR DURING NAMING REGISTRATION, BUT APP REGISTERS OK. | |||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description During Naming Registration of an application the following erro occurs in application server: . javax.naming.NameNotFoundException: [LDAP: error code 32 - R004026 Entry ibm-wsnName=com.ibm.ws390.wc.container. RemoteWebAppHome,ibm-wsnName=Delivery_WebApp,ibm-wsnName= Delivery_WebApp,ibm-wsnName=ERWW,ibm-wsnName=IBWJSR2, ibm-wsnName=UTCPLXB2,ibm-wsnName=legacyRoot, ibm-wsnName=UTCPLXB2,ibm-wsnName=domainRoots,ibm-wsnTree=t1, o=WASNaming,c=us not found in the database. (tdbm_search.c|1.74.2.2|767)];remaining name 'ibm-wsnName=com.ibm.ws390.wc.container.RemoteWebAppHome, ibm-wsnName=Delivery_WebApp,ibm-wsnName=Delivery_WebApp, ibm-wsnName=ERWW,ibm-wsnName=IBWJSR2,ibm-wsnName=UTCPLXB2' at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java . However, the LDAP namespace shows the above entry, and the application runs fine. . Defect #: MD14474(Pok) MD84036(Ral)Local fix Check if the entry showed by ldap 32 error as not found is in fact in ldap namespace. If so, and you are at level W401096 (ptf UQ69549, apar PQ62702) or later, you can ignore the error message. If you're below W401096, rycacle the server.Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V4.0.1 for z/OS and OS/390 * **************************************************************** * PROBLEM DESCRIPTION: "javax.naming.NameNotFoundException" * * with text "LDAP: error code 32" in a * * Server Region after installing a new * * Web application. * **************************************************************** * RECOMMENDATION: * **************************************************************** The customer defined a new Web application to an Application Server. In the subsequent bringup of the Application Server an associated Server Region received the following traceback indicating that the new Web application could not be found in LDAP: javax.naming.NameNotFoundException: LDAP: error code 32 - R004026 Entry ibm-wsnName=com.ibm.ws390.wc.container. RemoteWebAppHome,ibm-wsnName=Delivery_WebApp,ibm-wsnName= Delivery_WebApp,ibm-wsnName=ERWW,ibm-wsnName=IBWJSR1, ibm-wsnName=MONOSF5,ibm-wsnName=legacyRoot,ibm-wsnName= MONOSF5,ibm-wsnName=domainRoots,ibm-wsnTree=t1,o=WASNaming, c=US not found in the database. (tdbm_search.c|1.74.2.2|767) ; remaining name 'ibm-wsnName=com.ibm.ws390.wc.container. RemoteWebAppHome,ibm-wsnName=Delivery_WebApp,ibm-wsnName= Delivery_WebApp,ibm-wsnName=ERWW,ibm-wsnName=IBWJSR1, ibm-wsnName=MONOSF5' at com.sun.jndi.ldap.LdapCtx.mapErrorCode( LdapCtx.java:2775) at com.sun.jndi.ldap.LdapCtx.processReturnCode( LdapCtx.java:2696) at com.sun.jndi.ldap.LdapCtx.processReturnCode( LdapCtx.java:2502) at com.sun.jndi.ldap.LdapCtx.c_getAttributes( LdapCtx.java:1157) at com.sun.jndi.toolkit.ctx.ComponentDirContext. p_getAttributes(ComponentDirContext.java:228) at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext. getAttributes(PartialCompositeDirContext.java:137) at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext. getAttributes(PartialCompositeDirContext.java:125) at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext. getAttributes(PartialCompositeDirContext.java:115) at com.ibm.ws.naming.ldap.WsnLdapContextImpl.lookup( WsnLdapContextImpl.java:941) at com.ibm.ws.naming.ldap.WsnLdapContextImpl.lookup( WsnLdapContextImpl.java:1068) at javax.naming.InitialContext.lookup(InitialContext. java:359) at com.ibm.ws390.wc.container.WebContainer. getRemoteWebApps(WebContainer.java:127) at com.ibm.ws390.wc.container.WebContainer. httpSessionInvalidator(WebContainer.java:84) at java.lang.reflect.Method.invoke(Native Method) at com.ibm.ws390.WebContainerHook. httpSessionInvalidator(WebContainerHook.java:205) at com.ibm.ws390.rmi.corba.ORBEJSBridge. invokeWCSweeper(ORBEJSBridge.java:1170) at com.ibm.ws390.rmi.corba.ORBEJSBridge.initWCSweeper( ORBEJSBridge.java:1152) at com.ibm.ws390.rmi.corba.ORBEJSBridge.initOnce( ORBEJSBridge.java:985) at com.ibm.ws390.rmi.corba.ORBEJSBridge.threadInit( ORBEJSBridge.java:958) The function that was in control was looking for all defined WebApps. This was in control during Naming Registration for the newly defined WebApp(s). Since the new WebApp was not yet defined in LDAP the lookup failed. The function that was performing the lookups is involved in timing out HTTP Sessions.Problem conclusion Support has been modified to move the initial invocation of the WebContainer HTTP Session invalidator to a place after Naming Registration is complete. This will ensure that any lookups for newly defined Web applications will be successful. APAR PQ66407 is associated with SERVICE LEVEL W401402 of WebSphere Application Server V4.0.1 for z/OS and OS/390.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 401
Software edition:
Reference #: PQ66407
IBM Group: Software Group
Modified date: Nov 3, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.