PQ61098: INVALID CHARACTER IN THE JNDI PATH (BACKSLASH) CAUSES EXCEPTION CONVERTING JNDI NAME TO LDAP STRING NAME AT NAMING REGISTRATION | |||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||
APAR status Closed as fixed if next. Error description During Naming Registration of a new Application, which occurs the first time the application server is started after an app- lication is deployed, the following error was seen in the of the application server address space. The root cause of the problem is an invalid character in the JNDI name in the application. . Trace: 2002/05/02 14:17:50.018 01 t=9E4598 c=UNK key=P8 FunctionName: com.ibm.ws.naming.ldap.WsnLdapContextImpl SourceId: com.ibm.ws.naming.ldap.WsnLdapContextImpl Category: WARNING ExtendedMessage: Exception converting JNDI name to LDAP string JNDI name = PLEX1/BBOASR4/WebSphereSampleEARFile/default_app_ WebApp/abc\def Trace: 2002/05/02 14:17:51.315 01 t=9E4598 c=UNK key=P8 FunctionName: com.ibm.ws.naming.ldap.WsnLdapContextImpl SourceId: com.ibm.ws.naming.ldap.WsnLdapContextImpl Category: WARNING ExtendedMessage: Exception converting JNDI name to LDAP string JNDI name = PLEX1/BBOASR4/WebSphereSampleEARFile/default_app_ WebApp/abc\def javax.naming.InvalidNameException: Exception converting JNDI LDAP string same, JNDI name = ile/default_app_WebApp/abc\def. Root exception is javax.naming.InvalidNameException: in Name, the SinoJndiName Component contained delimiters at StringName(NameFormatHelper.java:237) at StringName(NameFormatHelper.java:145) at (WsnLdapContextImpl.java:1350) at com.ibm.ws.naming.ldap.WsnLdapContextImpl.bind (WsnLdapContextImpl.java:245) at javax.naming.InitialContext.bind(InitialContext.java:371) at com.ibm.ws390.util.JNDIRegisterer.registerHome (JNDIRegisterer.java:151)Local fix You can correct the JNDI Name in the SM/EUI, and re-deploy the application. The correction may also be made in the AAT (for 390 tool) then put through the SM/EUI, and re-deployed.Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V4.0 and V4.0.1 for z/OS and OS/390 * **************************************************************** * PROBLEM DESCRIPTION: Customer has entered an invalid * * character in the JNDI name field using * * either the Application Assembly Tool * * (AAT) tool for z/OS and OS/390 * * and/or SM EUI which never detects that * * it is invalid for the WebSphere 390 * * runtime. Error, * * javax.naming.InvalidNamingException, * * is currently being thrown during * * naming registration. Invalid JNDI * * name should be detected in 390 AAT * * and SM EUI to avoid such runtime * * error. * **************************************************************** * RECOMMENDATION: * **************************************************************** The AAT tool for z/OS and OS/390 and SM EUI should be fixed to detect invalid characters in JNDI name field before the deployment of a J2EE application in order to avoid runtime exception, InvalidNamingException, during naming registration.Problem conclusion Temporary fix Comments This APAR is being closed FIN with concurrence from the submitting customer. A solution to this problem will be delivered in an Application Assembly Tool (AAT) for z/OS and OS/390 driver within the next 18 months.
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 #: PQ61098
IBM Group: Software Group
Modified date: Jun 19, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.