PQ65687: SECURITY EXCEPTIONS AFTER SERVER REBOOTS | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description We are currently having intermittent problems with the IBM WAS Admin service not starting, especially after server reboots. This generates the following entry in sas_server.log: . 1> [2002-07-24 14:23:16.772], [ServerID: 12221999], [SecurityTaggedComponentAssistorImpl.register], Thread Hash: 673378419 Thread[P=596272:O=0:CT,5,main]: . JSAS0026E: Exception connecting object to the ORB. Check the sas.server.props file to ensure that the SSL keyStore and trustStore properties are set properly. If the problem persists, contact support for assistance. . We did apply the following fix found from the IBM Websphere support site but the problem still recurs. Solution . Put the following parameters in separate lines in the <WAS root>/bin/admin.config and set them to unique unused ports on the machine and restart WAS: . com.ibm.CORBA.SSLPort=<unique port #> com.ibm.CORBA.LSDSSLPort=<uniquie port #> . Problem occurs on WAS AE 4.03 and 4.04.Local fix no workaround availableProblem summary **************************************************************** * USERS AFFECTED: All WebSphere Users that have enabled * * security and restart their adminstration * * server while their application servers are * * up and running. * **************************************************************** * PROBLEM DESCRIPTION: If application server is up and * * running while the adminstration server * * is restarted, then application server * * continues to uses a stale IOR without * * loading the newly created one. * **************************************************************** * RECOMMENDATION: * **************************************************************** If the WebSphere Application Servers are up and running while the Admin Server is rebooted; then the Application servers continue to use the stale IOR for the Adminstration Server instead of getting the new IOR for the Adminstration Server. With the stale IOR, the Application Servers get OBJECT_NOT_EXIST exceptions.Problem conclusion To resolve this problem, the bootstrap repository is read to load the new IORs for the server that was restarted. The logic is to read the bootstrap repository to get the IORs up to three times and ping the server with the new IOR. After three times, if the server does not respond to the new IOR, then OBJECT_NOT_EXIST exception is thrown.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
SRLS
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ65687
IBM Group: Software Group
Modified date: Sep 26, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.