Fixes are available
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
The compression filter code is expecting a Content-Type header. If a response does not have one because it has no response data a NullPointerException will occur and a 500 status code is returned instead of the original status code. In the logs, the following FFDC entry will be generated: [5/4/12 19:34:56:576 GMT] FFDC Exception:java.lang.NullPointerException SourceId:com.ibm.ws.proxy.filter.http.HttpFilterChain.doResponse FilterChain ProbeId:1 Reporter:com.ibm.ws.proxy.filter.http.HttpFilterChain@616f1aa java.lang.NullPointerException at com.ibm.ws.proxy.compression.http.HttpCompressionFilter.getCompr essionMode(HttpCompressionFilter.java:76) at com.ibm.ws.proxy.compression.http.HttpResponseCompressionFilter. doFilter(HttpResponseCompressionFilter.java:113)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.0 and V8.5 Proxy Server. * **************************************************************** * PROBLEM DESCRIPTION: If the Proxy Server is configured for * * compression, a response with no * * Content-Type header will cause an NPE * * and a 500 response to be sent back. * **************************************************************** * RECOMMENDATION: * **************************************************************** The Proxy compression filter code expects inspects the Content-Type header on the response without checking if it exists. This causes an NPE and an FFDC. [5/4/12 19:34:56:576 GMT] FFDC Exception:java.lang.NullPointerException SourceId:com.ibm.ws.proxy.filter.http.HttpFilterChain.doResponse FilterChain ProbeId:1 Reporter:com.ibm.ws.proxy.filter.http.HttpFilterChain@616f1aa java.lang.NullPointerException at com.ibm.ws.proxy.compression.http.HttpCompressionFilter.getCompr essionMode(HttpCompressionFilter.java:76) at com.ibm.ws.proxy.compression.http.HttpResponseCompressionFilter. doFilter(HttpResponseCompressionFilter.java:113)
Problem conclusion
The Proxy Compression Filter will be changed to handle no Content-Type response header. APAR PM64028 is currently targeted for inclusion in Fix Packs 8.0.0.5 and 8.5.0.1 of WebSphere Application Server. Sysroute APAR PM66048 will be used to deliver this fix in WebSphere Application Server V7.0 for z/OS. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 In addition, please refer to URL: http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack PTF information.
Temporary fix
Comments
APAR Information
APAR number
PM64028
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-05-07
Closed date
2012-06-01
Last modified date
2012-08-17
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500
Applicable component levels
R800 PSY
UP
Document Information
Modified date:
28 October 2021