PQ60838: BROWSER HANGS USING HTTP TRANSPORT WITH PERSISTENT CONNECTIONS ON WEBSPHERE APPLICATION SERVER V4.0.1 FOR Z/OS AND OS/390

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
When using the HTTP Transport mechanism within WebSphere
Application Server V4.0.1 for z/OS and os/390, using persistent
connections, the browser will 'hang' until the persist timer
pops. This is because the Web container does not properly close
the connection after sending the data to the client, and it will
only be closed when the persist timer pops.
Another symptom that has been reported is performance
degradation when running a JSP.  One customer reported
that it took 29.7 seconds according to the sniffer trace
after the request got to the host.
NOTE: This APAR addresses Netscape and Internet Explorer
browsers.  Another problem, which a customer seemed to
circumvent by adding the BBOC_HTTP_SESSION_GC=1 to their
current.env file, was multiple frames getting displayed on
the browser.  They put the above setting in their current.env
file and that problem was resolved.
The setting BBOC_HTTP_SESSION_GC=1 merely turns off
persistent connections.  Please be aware that the name of
this directive will be changing with this APAR. The closure
of the APAR will document the new name.
-------------------------------------------------------------HB-
ADDITIONAL INFORMATION:
The new directive is BBOC_HTTP_MAX_PERSIST_REQUESTS
Accepting an int value indicating the max number of HTTP request
that will be processed over a single connection from an HTTP
client. When the maximum number of requests have been processed,
the client connection will be closed. Set this value to 0 or 1
to turn off persistent connection processing. The default value
is 50.
The previous directive BBOC_HTTP_SESSION_GC will continue to
be accepted unless both directives have been supplied.  In that
case BBOC_HTTP_MAX_PERSIST_REQUESTS will be used.
----------------------------------------------------------------
Local fix
Set this parm in current.env:
BBOC_HTTP_SESSION_GC=1
This disables persistent connections.
Problem summary
****************************************************************
* USERS AFFECTED: All users of the WebSphere Application       *
*                 Server Version 4.0.1 for z/OS or OS/390      *
*                 using the HTTP Transport Handler.            *
****************************************************************
* PROBLEM DESCRIPTION: When using the HTTP Transport Handler   *
*                      within WebSphere Application Server     *
*                      V4.0.1 for z/OS and  OS/390 using       *
*                      persistent connections, the browser     *
*                      will 'hang' until elapse time specified *
*                      for the persistent timer expires.       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
This condition occurs because the Web container does not
properly close the connection after sending the data to the
client. The connection will only be closed when the elapsed
time specified for the persist timer expires.  Then the Web
container should tell the HTTP Transport Handler to close the
connection when HTTP Header "Connection" is set to close.
Problem conclusion
The Web container code was changed so that if the HTTP Header
"Connection" is set to close, the Web container will send
a signal to the HTTP Transport Handler to close the connection.
This change affects CompID 5655A9800 for z/OS AND OS/390.
The code changes are stored in CMVC under defect PQ60838.

401Y
EJSJWCWC

* Cross Reference between External and Internal Names
Temporary fix
*********
* HIPER *
*********
++APAR AQ60838 has been supplied to the customer.
Comments
APAR information
APAR number PQ60838
Reported component name WEBSPHERE OS/39
Reported component ID 5655A9800
Reported release 401
Status CLOSED PER
PE NoPE
HIPER YesHIPER
Submitted date 2002-05-06
Closed date 2002-06-17
Last modified date 2002-09-17

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
EJSJWCWC          

Fix information
Fixed component name WEBSPHERE OS/39
Fixed component ID 5655A9800

Applicable component levels
R401 PSY UQ90049    UP02/06/28 P F206

  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


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 401
Software edition:
Reference #: PQ60838
IBM Group: Software Group
Modified date: Sep 17, 2002