PQ58365: 4.0 SHIPS WITH CORBA TIMEOUTREQUEST VALUES SET TO INFINITY {DEFAULT REQUESTTIMEOUT AND LOCATEREQUESTTIMEOUT} | |||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||
![]() APAR status Closed as documentation error. Error description The scenario is that in a multi node domain one host experiences a crash. Healthy node can not stop and restart due to default re questTimeout and locateRequestTimeout of the admin service bein g set to Infinity. Healthy node will attempt to communicate with Unhealthy node waiting for a response to it's request. With a va lue set to Infinity this prevents a Healthy node from continuing the process of starting the AdminService. A more approriate valu e for the customer is 200 = 3.2 minutes.Local fix Workaround: Manually modify admin.config file adding: com.ibm.CORBA.requestTimeout=200 com.ibm.CORBA.locateRequestTimeout=200Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server users who are * * trying to set ORB timeout values that will * * apply to the WebSphere administrative * * server. * **************************************************************** * PROBLEM DESCRIPTION: Although there are some references in * * InfoCenter to the two timeouts * * referenced here, there are no hits * * when user does a search. * * Additionally, the references only * * describe using these timeout values * * but fail to define them. * **************************************************************** * RECOMMENDATION: * **************************************************************** Based on a user's network latency as well as types of applications involved, the user may need to adjust the values of timers for the WebSphere administrative server. For application servers, we document how this should be done but for the administrative server, it is not clear. This creates confusion for users and results in additional calls to IBM support.Problem conclusion Documentation defect created with requesting that we add the definitions of: com.ibm.CORBA.requesttimeout com.ibm.CORBA.locaterequestTimeout to the WebSphere InfoCenter section section titled "Administrative server configuration file properties" as well as some guidance in when/why setting these values might be appropriate. Also, requested that InfoCenter search should return relevant sections of documentation when we search on "requesttimeout" or "locaterequesttimeout".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 #: PQ58365
IBM Group: Software Group
Modified date: Mar 24, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.