PQ57066: CUSTOM REGISTRY IS INITIALIZED MULTIPLE TIMES WHEN STARTING THE APP SERVER. | |||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||
APAR status Closed as program error. Error description Here are the details from the pmr: . Abstract: Custom Registry inappropriately initialized . System Type: Solaris Operating System: SUN Product Group: WebSphere Application Server AE SUN 400 . Environment: I do not believe this is environment specific, but I have tested only on Solaris. Solaris 2.8, WebSphere Application Server 4.0.1, Oracle 8.1.7, iPlanet Security enabled, using Trusted Associations and Custom Registr . Problem: I have written a custom registry for WebSphere Application Server. The registry is working fine, however, I have discovered a problem in the Application Server that may lead to resource leaks: the registry is being initialized *4 times* in the app server. This is wrong for two reasons: 1) initing it 4 times is just bizarre 2) the custom registry isn't used by the app server . When I start an admin server, the custom registry is initialized exactly once as I would expect. There are no problems. Every single time I start *any* application server I see the registry initialized 4 times. I know this for two reasons: . 1) I have tracing in my registries init() method that outputs information every time init is called. 2) the WebSphere Application Server Audit subsystem prints the following audit message every time the registry is initialized (4 times when starting an app server): . SECJ0136A: Custom Registry com.ibm.swservices.websphere.registry.Mul tiLDAPCustomRegistry has been initialized. The "com.ibm.*.MultiLDAPCustomRegistry" stuff is the name of my registryLocal fix Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server security users. * **************************************************************** * PROBLEM DESCRIPTION: Security registry properties are * * initialized multiple times. * **************************************************************** * RECOMMENDATION: * **************************************************************** security registry properties are initialized multiple times, and they should only be initialized once. The unnecessary initializations are harmless but can lead to confusion on the part of an implementer of a Custom registry. Initialization should only occur once.Problem conclusion A redundant registry initialization call was removed.Temporary fix send testing efix to customer.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 > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ57066
IBM Group: Software Group
Modified date: Apr 29, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.