PQ59529: SM EUI ALLOWS A // IN JNDI NAME WHICH CORRUPTS DATABASE | |||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description User made changes to application and attempted to redeploy. Added new conversation etc. made a keying error in the JNDI name, two slashes... /FORWARD/BBOASR1/ETFTestRoutines2/ETFTestRoutines2Web_WebApp/ETF ines2Web_WebApp//ETFTestRoutines2Web This caused the attempt at naming registration to fail. BBOU0700I DEREGISTERING COMPONENT ETFTestRoutines2Web_WebApp FOR SERVER BBOASR1 BBOU0697I REGISTERING COMPONENT ETFTestRoutines2Web_WebApp FOR S BBOASR1 BBOU0652E NAMING REGISTRATION FAILED FOR SERVER BBOASR1 .Local fix prepare for cold startProblem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V4.0.1 for z/OS and OS/390 * **************************************************************** * PROBLEM DESCRIPTION: After the customer installed an * * application with a JNDI name containing * * a double-slash ("//"), the server * * failed during activation and restart * * with the following message: * * "BBOU0652E NAMING REGISTRATION FAILED * * FOR SERVER BBOASR1". * * The customer was forced to do a cold * * start to recover. * **************************************************************** * RECOMMENDATION: * **************************************************************** The customer used the System Management End User Interface (Administration and Operations applications), also known as the SM EUI, to install an application, and accidentally typed a name with a double-slash ("//") for one of the component's JNDI names (the full JNDI name was "/FORWARD/BBOASR1/ETFTestRoutines2 /ETFTestRoutines2Web_WebApp/ETFines2Web_WebApp //ETFTestRoutines2Web"). The customer activated the conversation, which caused the server on which the application was deployed, BBOASR1, to restart. During the restart, the server failed with the message: "BBOU0652E NAMING REGISTRATION FAILED FOR SERVER BBOASR1". The customer then tried to delete the application by creating and activating a new conversation. The server still failed to start with the naming registration error cited above, and the customer was forced to do a cold start.Problem conclusion Method upsertComponentNamingRegistrationEntry() in bbomsbo7.cpp contained a logic error. Instead of preserving the previous naming entry in the OLD_HOME_STRING field of the BBO.BBOMT84_NAMREG table, the code was storing the contents of the HOME_STRING field there in the case of deleting an application. Under the customer's problem scenario, this led to a situation where invalid naming entries containing "//" were stored in both the HOME_STRING and OLD_HOME_STRING fields. This, in turn, prevented the "rollback" to a valid state that should have occurred when the application was deleted. The upsertComponentNamingRegistrationEntry() method was fixed to preserve the naming entry in the OLD_HOME_STRING field of the BBO.BBOMT84_NAMREG table in the case of deleting an application. This allows for the successful deletion of the application that contains an invalid naming entry. APAR PQ59529 is associated with SERVICE LEVEL W401044 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: UQ65084 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 #: PQ59529
IBM Group: Software Group
Modified date: May 2, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.