PQ94005: Cannot set ORB requestTimeout to a value higher than 300 seconds.

 Fixes are available

PQ94005; 5.0.2: Cannot set ORB requestTimeout and locateRequestTimeout greater t
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for AIX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Windows
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for HP-UX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Solaris
5.1.1.6: WebSphere Application Server Version 5.1.1 Cumulative Fix 6
5.1.1.7: WebSphere Application Server Version 5.1.1 Cumulative Fix 7
5.1.1.4: WebSphere Application Server Version 5.1.1 Cumulative Fix 4
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Linux



APAR status
Closed as program error.

Error description
Customer cannot change the ORB requestTimeout value to a number
higher than 300 seconds.  The Admin Console will not allow a
value higher than 300 to be input, abd if you try and set the
com.ibm.CORBA.requestTimeout manually to a value higher than
300, the ORB code defaults the value to 300.   Since it can be
set to 0, making it unlimited, there is no reason to have an
artificial top value of 300.  locateRequestTimeout also needs to
allow a value higher than 300.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users requiring *
*                 a requestTimeout or a locateRequestTimeout   *
*                 of greater than 300 seconds.                 *
****************************************************************
* PROBLEM DESCRIPTION: There used to be a limit of 300 seconds *
*                      for requestTimeout and                  *
*                      locateRequestTimeout. This restriction  *
*                      has been removed.                       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The ORB had a maximum of 300 seconds for requestTimeout and
locateRequestTimeout.  If a value larger than that was
specified, the ORB would ignore it and just use 300.
Problem conclusion
The 300 second limit was removed.  The new practical limit
is MAX_INT.
The code change was in the base orb family.
The fix for this APAR is currently targeted for inclusion in fix
pack 5.0.2.10 and 5.1.1.3. Please refer to the
  Recommended Updates page for delivery dates:
  
http://www-1.ibm.com/support/docview.wss?rs=180&context=SSEQTP
&uid=swg27004980
Temporary fix Comments
APAR information
APAR number PQ94005
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00A
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-09-09
Closed date 2005-01-17
Last modified date 2005-01-17

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
ORB          

Publications Referenced

Fix information

Applicable component levels
R10I PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00P PSY    UP
R00S PSY    UP
R00W PSY    UP
R10A PSY    UP
R10H PSY    UP
R10P PSY    UP
R10S PSY    UP
R10W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00A
Software edition:
Reference #: PQ94005
IBM Group: Software Group
Modified date: Jan 17, 2005