PQ49545: NO MESSAGES TO USER WHEN NAMING REGISTRATION FAILS | |||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description After installing an application on a server and activating the conversation with that new ejb application, the customer tried to start the server. It attempted to register the application and got a naming registration failed exception. There were no messages to indicate why it failed. The customer turned on TRACEALL=3, but it did not give much more than a home not createable trace message and you could see the ior returned was 0. After turning on Tr tracing for the application server, that it could not find classes associated with Visual Age Persistence. It should be more obvoius to the user, without having to turn on any trace as to what the problem is.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V4.0 for z/OS and OS/390. * **************************************************************** * PROBLEM DESCRIPTION: Insufficient diagnostics when naming * * registration of an ejb fails. * **************************************************************** * RECOMMENDATION: * **************************************************************** WebSphere for z/OS attempts to register the homes of a newly imported EJB application into the JNDI name space the first time the server where the EJB was installed is started. This is indicated by the following message: BBOU0694I NAMING REGISTRATION STARTED FOR SERVER <servername> When the naming registration failes, then the following message is issued: BBOU0652E NAMING REGISTRATION FAILED FOR SERVER <servername> No indication is given as to why the registration failed. It is typically due to missing classes during the loading of the bean meta data. The missing class name can only be found by turning on trace and best found by turning on java trace (JVM_DEBUG=1). It should be more apparent to the user why the failure occurred.Problem conclusion New message, BBOJ0016E will be issued to report ClassNotFound exceptions. The message will indicate the name of the EJB being processed as well as the name of the missing class. The following publication was revised as a result of APAR PQ49545: ________________________________________________________________ WebSphere Application Server V4.0 for z/OS and OS/390 Messages and Diagnosis GA22-7837-00 ________________________________________________________________ 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 12, pg. 198 (new message) BBOJ0016E Could not load EJB <beanname> - Class <beanclass> not found. Explanation: An error message issued when loading an EJB. The specified class could not be found. Programmer response: Add missing class to the EJB jar file and re-install J2EE application. _______________________________________________________________ APAR PQ49545 is associated with SERVICE LEVEL W400043 of WebSphere Application Server V4.0 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: UQ58167 Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ49545
IBM Group: Software Group
Modified date: Nov 2, 2001
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.