IBM Support

PM48806: HTTP 4XX ERRORS CHANGED TO 5XX ERRORS ON Z/OS

Fixes are available

7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
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.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.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
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
Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Some HTTP error codes that were returned as 4xx codes On
    WebSphere Application Server z/OS version 6.0.2 are returned
    as 5xx codes on versions 6.1 and above.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0 and V8.0.                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: Applications might return               *
    *                      HTTP 5xx codes  when they               *
    *                      previously returned 4xx codes           *
    *                      running under WebSphere version 6.0.2   *
    ****************************************************************
    * RECOMMENDATION:  Install a fixpack containing this APAR.     *
    ****************************************************************
    An unexpected 5xx http code is received by a client.
    The inbound HTTP message that produced the 5xx error will not
    contain a CONTENT-LENGTH HTTP  header.
    In the  server-side ffdc logs, this stack might be observed:
    FFDC Exception:java.lang.IndexOutOfBoundsException
    SourceId:HttpInboundLink.handleDiscrimination ProbeId:1
    Reporter:com.ibm.ws.http.channel.inbound.impl.HttpInboundLink@53
    3b533b
    java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
    at java.util.ArrayList.get(ArrayList.java:352)
    at
    com.ibm.ws.soapchannel.monitor.impl.SOAPMonitorChannelInputStrea
    m.rewind
    (SOAPMonitorChannelInputStream.java:237)
    at
    com.ibm.ws.soapchannel.monitor.impl.SOAPMonitorChannelInputStrea
    m.getByt
    eBuffers(SOAPMonitorChannelInputStream.java:245)
    at
    com.ibm.ws.soapchannel.monitor.impl.SOAPRequestMonitorServiceCon
    text.getByteBuffers(SOAPRequestMonitorServiceContext.java:141)
    at
    com.ibm.ws.soapchannel.monitor.impl.SOAPConnectionLink.doApplica
    tionSide
    Dispatch(SOAPConnectionLink.java:185)
    at
    com.ibm.ws.soapchannel.monitor.impl.SOAPConnectionLink.ready(SOA
    PConnect
    ionLink.java:164)
    at
    com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscr
    iminatio
    n(HttpInboundLink.java:445)
    or this one
    FFDC Exception:java.lang.RuntimeException
    SourceId:HttpInboundLink.handleDiscrimination ProbeId:1
    Reporter:com.ibm.ws.http.channel.inbound.impl.HttpInboundLink@49
    bf49bf
    java.lang.RuntimeException: WSSC1005E: Caught unexpected
    exception from
    synchronous getRequestBodyBuffers():
    com.ibm.wsspi.http.channel.exception.IllegalHttpBodyException:
    Non-length delimited body on request
    at
    com.ibm.ws.soapchannel.monitor.impl.SOAPMonitorChannelInputStrea
    m.nextBu
    ffer(SOAPMonitorChannelInputStream.java:223)
    at
    com.ibm.ws.soapchannel.monitor.impl.SOAPMonitorChannelInputStrea
    m.<init>
    (SOAPMonitorChannelInputStream.java:78)
    at
    com.ibm.ws.soapchannel.monitor.impl.SOAPRequestMonitorServiceCon
    text.ini
    t(SOAPRequestMonitorServiceContext.java:95)
    at
    com.ibm.ws.soapchannel.monitor.impl.SOAPConnectionLink.processRe
    quest(SO
    APConnectionLink.java:246)
    at
    com.ibm.ws.soapchannel.monitor.impl.SOAPConnectionLink.ready(SOA
    PConnect
    ionLink.java:156)
    at
    com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscr
    iminatio
    n(HttpInboundLink.java:445)
    

Problem conclusion

  • SOAPMonitorChannelInputStream was not correctly resetting
    buffers under some conditions. The code has been corrected.
    
    A JVM property must be set to enable the new behavior,
    set com.ibm.webservices.zos.preferHttp4xx to a value of true.
    
    APAR PM48806 requires changes to documentation.
    
    NOTE: Periodically, we refresh the documentation on our
    Web site, so the changes might have been made before you
    read this text. To access the latest on-line
    documentation, go to the product library page at:
    
    http://www.ibm.com/software/webservers/appserv/library
    
    The following changes to the WebSphere Application Server
    Version 7.0 Information Center will be made available in
    September, 2012.
    
    The topic "Java virtual machine custom properties" will
    be updated to include the following description of the
    com.ibm.webservices.zos.preferHttp4xx custom
    property:
    
    com.ibm.webservices.zos.preferHttp4xx
    
    Use this property to specify whether the JVM returns an
    HTTP 5xx or an HTTP 4xx return code if a web service
    message is missing a CONTENT-LENGTH HTTP header.
    
    On the z/OS operating system, an application might return
    an HTTP 5xx return code if a web service message is
    missing a CONTENT-LENGTH HTTP header. On the other
    supported operating systems, the application returns an
    HTTP 4xx return code if a web service message is missing
    a CONTENT-LENGTH HTTP header.
    
    If you a want the application to always return an HTTP 4xx
    regardless of the operating system on which the application
    is running, add this property to the JVM settings for the
    controller, and set it to true.
    
    APAR PM48806 is currently targeted for inclusion in
    Fix Packs 7.0.0.23 and 8.0.0.4 of WebSphere Application
    Server.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM48806

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-09-27

  • Closed date

    2012-02-24

  • Last modified date

    2012-06-03

  • 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

  • R700 PSY UK78616

       UP12/05/26 P F205

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

More support for: WebSphere Application Server for z/OS
General

Software version: 7.0

Reference #: PM48806

Modified date: 03 June 2012