PQ78849: USER IS USING JAVA WEB START TO GET A FILE FROM SERVER. SERVER IS RUNNING EMBEDDED WEBSPHERE APPSERVER EXPRESS V5.0. THE SERVER

 Fixes are available

PQ81764: Configuring the trusted mode to determine private HTTP headers
5.1.0.5: WebSphere Application Server Express 5.1 Cumulative Fix 5
PQ78849; 5.0.2.2: IllegalState exception when HEAD request is issued.
5.0.2.7: WebSphere Application Server Express 5.0.2 Cumulative Fix 7
5.0.2.12: WebSphere Application Server 5.0.2 Cumulative Fix 12
5.0.2.13: WebSphere Application Server 5.0.2 Cumulative Fix 13
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for AIX
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for Solaris
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for HP-UX
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for Windows
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for Linux
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for Windows
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for Solaris
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for AIX
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for Linux
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for HP-UX
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for HP-UX
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for AIX
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for Solaris
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for Windows
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for Linux
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for AIX
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for HP-UX
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Linux
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Windows
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Solaris
5.0.2.8: WebSphere Application Server V5.0.2 Cumulative Fix 8
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for HP-UX
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for AIX
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Solaris
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Windows
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Linux
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Windows
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Solaris
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for HP-UX
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Linux
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for AIX



APAR status
Closed as program error.

Error description
User is using Java Web Start to get a file from server. Server
is running Embedded Websphere Appserver Express v5.0. The server
is set to use SSL.JWS sends in a GET request to retrieve a fil
e.  As part of the GET request, WebSphere does an HTTP HEAD requ
est.  A Head request returns the headers of a get request but no
BODY was written.  This causes the socket to close and get the f
ail even though the file was available. The fix was in to specia
l transport HEAD requests to recognize that 0 bytes of body woul
d be written. A work around solution is available from Ali Goins
Local fix
See Ali Goins of the HTTPL3 team.
Problem summary
****************************************************************
* USERS AFFECTED: Any user whose client sends a HEAD request   *
*                 to a static file.                            *
****************************************************************
* PROBLEM DESCRIPTION: The following IllegalStateException     *
*                      occurs in the log file:                 *
*                      0 response bytes written, but           *
*                      Content-Length header equals XXX        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
This is the result of a bug in the code.  The exception is
thrown because 0 response bytes are written when the file has
a Content-Length, however this is working as designed since
no bytes are supposed to be written for a HEAD request.
Problem conclusion
Code changed to not throw the IllegalStateException when a
HEAD request is issued.
Temporary fix Comments
APAR information
APAR number PQ78849
Reported component name WAS-EXPRESS WIN
Reported component ID 5724D06WN
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2003-09-24
Closed date 2003-11-05
Last modified date 2003-11-05

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
utils          

SRLS

Fix information
Fixed component name WEBPSHERE AE HP
Fixed component ID 5630A2203

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ78849
IBM Group: Software Group
Modified date: Nov 5, 2003