IBM Support

PK86608: ACCEPT MESSAGE CONTAINS INCORRECT CONTENT-TYPE

Fixes are available

7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for AIX
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for IBM i
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for Windows
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for HP-UX
7.0.0.5: Java SDK 1.6 SR5 Cumulative Fix for WebSphere Application Server
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for Solaris
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for Linux
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for IBM i
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for AIX
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Windows
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for HP-UX
7.0.0.7: Java SDK 1.6 SR6 Cumulative Fix for WebSphere Application Server
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Solaris
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Linux
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for IBM i
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Windows
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for AIX
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for HP-UX
7.0.0.9: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Solaris
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Linux
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
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
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
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

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An HTTP accept message contains an incompatible Content-Type
    (SOAP 1.1) for SOAP 1.2 requests. This may result in
    interoperability errors for 2-way asynchronous messages or
    HTTP 202 acknowledge messages.
    
    Example wire trace for the incoming request message:
    
    POST
    /IBM_WS_SYS_RESPONSESERVLET/RspEAR:RSPClient.war/services/
    RspService12.RspService12 HTTP/1.1
    
    Content-Type: application/soap xml; charset=utf-8
    Host: ws2.acme.com:9080
    Content-Length: 778
    Expect: 100-continue
    Connection: Keep-Alive
    HTTP/1.1 100 Continue
    Content-Length: 0
    Date: Tue, 12 May 2009 18:24:47 GMT
    Server: WebSphere Application Server/7.0
    Date: Tue, 12 May 2009 18:24:47 GMT
    
    Example incoming wire trace for the acknowledgment:
    
    Server: WebSphere Application Server/7.0
    Content-Type: text/xml; charset=utf-8
    IBM-WAS-Reset-Connection: TRUE
    Content-Language: en-US
    Set-Cookie: JSESSIONID=0000zNxk_c2GW_Mr7c0hlXC1cl6:-1; Path=/
    Transfer-Encoding: chunked
    Expires: Thu, 01 Dec 1994 16:00:00 GMT
    Cache-Control: no-cache="set-cookie, set-cookie2"
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server users of   *
    *                  JAX-WS applications                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: The HTTP accept message from the        *
    *                      Websphere Application Server contains   *
    *                      an incompatible HTTP Content-Type.      *
    ****************************************************************
    * RECOMMENDATION:  Install a FixPack containing this APAR on   *
    *                  the server sending the response or          *
    *                  acknowledgement message.                    *
    ****************************************************************
    JAX-WS web services support both SOAP 1.1 and SOAP 1.2
    protocols.  When the WebSphere Application Server JAX-WS
    runtime receives a SOAP 1.2 request, it should respond with a
    SOAP 1.2 message or acknowledgement.
    
    A SOAP 1.1 message will have the value "text/xml" in the HTTP
    MIME Content-Type Header.
    A SOAP 1.2 message will have the value "application/soap xml"
    in the HTTP MIME Content-Type Header.
    
    When a client web service application calls a SOAP 1.2 web
    service hosted on the WebSphere Application Server, the JAX-WS
    runtime may respond with a SOAP 1.1 message.  This may cause
    an error on the client receiving the message.
    
    Example request message received on the WebSphere Application
    Server:
    
    
    POST
    /IBM_WS_SYS_RESPONSESERVLET/RspEAR:RSPClient.war/services/
    RspService12.RspService12 HTTP/1.1
    
    Content-Type: application/soap xml; charset=utf-8
    Host: ws2.acme.com:9080
    Content-Length: 778
    Expect: 100-continue
    Connection: Keep-Alive
    HTTP/1.1 100 Continue
    Content-Length: 0
    Date: Tue, 12 May 2009 18:24:47 GMT
    Server: WebSphere Application Server/7.0
    Date: Tue, 12 May 2009 18:24:47 GMT
    
    Example, invalid response sent from the WebSphere Application
    Server:
    
    Server: WebSphere Application Server/7.0
    Content-Type: text/xml; charset=utf-8
    IBM-WAS-Reset-Connection: TRUE
    Content-Language: en-US
    Set-Cookie: JSESSIONID=0000zNxk_c2GW_Mr7c0hlXC1cl6:-1; Path=/
    Transfer-Encoding: chunked
    Expires: Thu, 01 Dec 1994 16:00:00 GMT
    Cache-Control: no-cache="set-cookie, set-cookie2"
    
    
    If the client application is using a different vendor to
    receive the web service message, the vendor's runtime may fail
    due to a SOAP version mismatch.
    
    The root of the problem is the IBM JAX-WS engine is sending
    an incompatible Content-Type value.
    

Problem conclusion

  • The IBM JAX-WS runtime contained code to send a
    asynchronous response or acknowledge message with a
    Content-Type set to the SOAP 1.1 protocol.   This code was
    changed to send the response or acknowledgment message with a
    Content-Type that matches the Content-Type of the incoming
    message.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.5.  Please refer to the Recommended Updates
    page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK86608

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-05-14

  • Closed date

    2009-05-28

  • Last modified date

    2009-05-28

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 October 2021