PQ73967: APPLICATION SERVER ORB INITIALIZES WITH REQUEST TIMEOUT = 0 ALTHOUGH "REQUEST TIMEOUT" OF 180 IS SHOWN IN CONSOLE | |||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description In WebSphere V4.0 if the application server Object Request Broker (ORB) request timeout setting is allowed to default to 180, the actual initialization of the application server ORB uses a request timeout of 0 (unlimited wait). Using the administration console, if you change the request timeout value within the Object Request Broker properties to any value other than 180, it is properly used by application server ORB initialization.Local fix Set System Properties for the application server to the desired request timeout value, rather than using the Services / Object Requent Broker / Edit Properties method. Bypass: While displaying the application server properties: 1) click on JVM Settings 2) scroll down to "System Properties" 3) click "Add" and insert the following "Name" and "Value" 4) (Name) com.ibm.CORBA.requestTimeout (Value) 180 5) Click "Apply" Note: The same method can be used to set com.ibm.CORBA.locateRequestTimeout. Normally the requestTimeout and locateRequestTimeout settings are set to the same values.Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server users who * * configure ORB properties using the admin * * console. * **************************************************************** * PROBLEM DESCRIPTION: Application Server initializes * * with ORB RequestTimeout = 0, but * * the RequestTimeout is shown to be * * 180 on the console. * **************************************************************** * RECOMMENDATION: * **************************************************************** ORB RequestTimeout is inconsistent between value shown on the admin console (180), and what is actually used when the server initializes (0). If you change the RequestTimeout value to any value other than 180, the value shown on console is properly used by application server ORB initialization.Problem conclusion This fix corrects the inconsistency on the default ORB RequestTimeout value between console and runtime to ensure the intended value is actually used when the server initialized. It also corrects the ORB default RequestTimeout to be 0 if no previous value had persisted.Temporary fix Sent customer test fix, waiting for feedbackComments
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 #: PQ73967
IBM Group: Software Group
Modified date: May 20, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.