PQ61096: INVALID CHARACTER IN THE JNDI PATH (BACKSLASH) CAUSES EXCEPTION CONVERTING JNDI NAME TO LDAP STRING NAME AT NAMING REGISTRATION | |||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. 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 output 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.Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V4.0.1 for z/OS and OS/390 * **************************************************************** * PROBLEM DESCRIPTION: The System Management End User * * Interface (Administration and * * Operations applications), also known as * * the SM EUI, allows an illegal JNDI path * * and name combinations to be entered * * during resource and reference * * resolution. During registration, the * * strings caused an exception in the * * container code. * * * * APAR PQ61096 also addresses the * * following defect: * * * * (MD13890) When installing a J2EE * * application the SM EUI checks if * * every method on a bean had a * * transaction attribute specified * * inside of the deployment descriptor. * * If that was not the case the * * installation of the application * * was prevented. This checking was too * * restrictive. * **************************************************************** * RECOMMENDATION: * **************************************************************** Since the installation was successful, the customer expected that all the information for his application was correct. During the naming registration, one JNDI name string did not make it past the registration code. Checking the JNDIname string in the System Management End User Interface (Administration and Operations applications), also known as the SM EUI, with the same algorithm would prevent this situation. APAR PQ61096 also addresses the following defect: (MD13890)When trying to install an application that does not have for all methods of a bean a transaction attribute specified error BBON0885E is surfacing asking to take the application ear file back to the Application Assembly Tool to add the missing transaction attributes. In some cases this is not even possible (e.g. getEJBHome()) since the Application Assembly Tool (AAT) does not allow the transaction attributes to be set to fulfill the J2EE specification and sometimes the wildcard "*" for the method names in the deployment descriptor is not interpreted correctly by the algorithm used.Problem conclusion The code used during naming registration is now used in the System Management End User Interface (Administration and Operations applications), also known as the SM EUI, to parse the JNDI name string to make sure it is valid. If one JNDI name string is invalid, the installation of the application will not be allowed. (MD13890)The checking has been removed from the SM EUI. Should a method of a bean have no transaction attribute specified, the default transaction attribute will be used. The following publication was revised as a result of APAR PQ61096: _______________________________________________________________ WebSphere Application Server V4.0.1 for z/OS and OS/390 Messages and Diagnosis GA22-7837-02 _______________________________________________________________ This APAR requires changes to documentation. NOTE: Periodically, we refresh the documentation on our Web site, so the changes might have been made before you read this text. To access the latest on-line documentation, go to the product library page at: http://www.ibm.com/software/webservers/appserv/ _______________________________________________________________ Chapter 9, pg. 147 (changed) BBON1104E Could not move source-file to destination-file. Explanation: The Prepare for cold start action or Activate action failed, because one of the configuration data files could not be moved. User Response: Make sure that the files in the following paths allow write access: "CBCONFIG/Sysplex_name/conversations/current" and "CBCONFIG/controlinfo/envfile/Sysplex_name/ServerInstance_name/" where - CBCONFIG is the path that you specified in the environment variable CBCONFIG. The default for CBCONFIG is /WebSphere390/CB390 Sysplex_name is the name of any sysplex ServerInstance_name is the name of any server instance that belongs to the sysplex _______________________________________________________________ APAR PQ61096 is associated with SERVICE LEVEL W401079 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: UQ67993 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 #: PQ61096
IBM Group: Software Group
Modified date: Aug 4, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.