PK16703: ILLEGALSTATEEXCEPTION THROWN WHEN THE CONTENT-TYPE IS NOT BEING SET FOR THE RESPONSE. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description HTTPTransport component throw an IllegalStateException when the content-type is not being set for response. java.lang.IllegalStateException: no Content-Type was specified at com.ibm.ws.http.HttpResponse.writeHeaders(HttpResponse.java: 281) at com.ibm.ws.http.ResponseStream.writeHeaders(ResponseStream.j ava: 230) at com.ibm.ws.http.ResponseStream.flushBuffer(ResponseStream.Local fix N/AProblem summary **************************************************************** * USERS AFFECTED: All Websphere Application Server users * **************************************************************** * PROBLEM DESCRIPTION: If the Content-Type HTTP header is not * * set for the response, the Http * * Transport will throw an * * IllegalStateException. * **************************************************************** * RECOMMENDATION: * **************************************************************** The Http Transport had implemented a HTTP compliance check for the presence of a Content-Type header in the response. If this header was not set for the response, an IllegaStateException is thrown by the HttpResponse.writeHeaders() method. Prior to APAR PK12004, the Webcontainer was setting a default Content- Type header when one was not set by the application. After PK12004 ( Websphere 5.1.1.9 ) the Webcontainer can be configured to not set a default Content-Type header which will cause this exception to be thrown if the application does not set the header. The exception seen in the trace or output logs is: java.lang.IllegalStateException: no Content-Type was specified at com.ibm.ws.http.HttpResponse.writeHeaders(HttpResponse.java:281)Problem conclusion This HTTP compliance check is not required for HTTP 1.0 or 1.1, so it has been removed from HttpResponse.writeHeaders(). The exception will no longer occur if a Content-Type header is not present in the response. This fix is currently targeted for inclusion in fixpacks 5.0.2.16 and 5.1.1.10. The problem is already fixed in version 6.0. Please refer to the recommended updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 10W
Software edition:
Reference #: PK16703
IBM Group: Software Group
Modified date: Jan 12, 2006
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.