PQ75657: ADD A CUSTOM PROPERTY SO THAT YOU CAN CONFIGURE THE HTTP OUTPUT TIMEOUT INDEPENDENTLY FROM THE INPUT TIMEOUT.

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
In attempting to deploy applications, customer receives:
AppDeploymentException:  com.ibm.etools.archive.exception
The problem is that because there is no http output, the
protocol_http_timeout_output trigger starts and after 120
seconds (default) the installation process abends.
Local fix
Setting protocol_http_timeout_output=600 on a server level
circumvents the problem.  This can be temporarily changed in
the was.env configuration file that must be entered manually.
The was.env file is overwritten by Admin Console changes.
Or it can be permanently changed in the Admin Console by
Environment -> Manage WebSphere Variables -> then select the
Server radio button and Apply; then select New and enter the
variable name to protocol_http_timeout_output with a value of
600.  Then save the changes to the master configuration and
recycle the server to pick up the change.  When the new
custom property can be used after this apar is applied,
use the custom property to set the http output timeout
value and do not explicitly set environment variable
protocol_http_timeout_output.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: In attempting to deploy applications,   *
*                      customer receives:                      *
*                      AppDeploymentException:                 *
*                      com.ibm.etools.archive.exception        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The application deployment is being timed by a timer
value used for http response which is by default 120 seconds.
When the timer expires, the installation process abends
and the AppDeploymentException is thrown. To adjust the timer
value, the custom property ConnectionIOTimeout will set both
input and response timers to the same value. A separate custom
property is needed to set the response timer value differently
from input timer value.
Problem conclusion
A new custom property has been added: ConnectionResponseTimeout
which sets the response timer value.
The ConnectionIOTimeout custom property will set only the
input timer now.
The defaults have also been modified, the
protocol_http_timeout_input and protocol_https_timeout_input
now defaults to 120, while the
protocol_http_timeout_output and protocol_https_timeout_output
now defaults to 300.

The following publication / InfoCenter article will be revised
as a result of APAR PQ75657:
________________________________________________________________
WebSphere Application Server for z/OS V5
Book name / InfoCenter
Book number / Article title
________________________________________________________________
NOTE: Periodically, we refresh the documentation on our
Web site, so these changes might have been made before you
read this text. To access the latest on-line
documentation, go to the product library page at:

www.ibm.com/software/webservers/appserv/zos_os390/library/
________________________________________________________________
Article title, Example: Setting custom properties for an HTTP
transport (new/changed/deleted text)

ConnectionIOTimeout

Specifies the maximum number of seconds to
wait when trying to read or process data during a request.
Data type: Integer.

This value determines how long to wait while receiving two
subsequent data packets for the same HTTP request. For example,
using the default ConnectionIOTimeout setting of five seconds,
if an HTTP client sends two data packets spaced six seconds
apart, the timeout will fire, and a
java.io.InterruptedIOException is raised. This will terminate
the HTTP request and it will not be read The HTTP client will
have to reissue the request. Default:
120 seconds.

If you specify a value for this property, the same value will be
used for the wait time for both reading and processing data
during a request.

ConnectionResponseTimeout

Specifies the maximum number of seconds to wait when trying to
read or write data during a response. Data type: Integer.
Default: 300 seconds.
________________________________________________________________

APAR PQ75657 is associated with SERVICE LEVEL W500103 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ75657
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-06-26
Closed date 2003-08-01
Last modified date 2003-09-05

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
BBOUBINF          

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UQ79132    UP03/08/08 P F308

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Current web document: swg1PQ75657.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ75657
IBM Group: Software Group
Modified date: Sep 5, 2003