IV14834: JAXWS AND MTOM FUNCTIONALITY FAILS ON NON-ASCII PLATFORMS LIKE Z/OS

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • When attempting to use a JAXB/JAXWS MTOM enabled web service,
    certain APIs are non-functional on z/OS.
    
    The stacktrace for this issue will show a failure to parse
    headers and/or the message itself:
    
    com.sun.xml.internal.ws.protocol.soap.MessageCreationException:
      Couldn't create SOAP message due to exception:
    java.lang.IllegalStateException:
    Internal Error. Didn't get Headers even after complete parsing.
     at com.sun.xml.internal.ws.encoding.SOAPBindingCodec.decode
     at com.sun.xml.internal.ws.transport.http.client.
          HttpTransportPipe.process
     at com.sun.xml.internal.ws.transport.http.client.
          HttpTransportPipe.processRequest
    ...
    
    This problem is due to incorrect encoding of strings between the
    default platform codepage (EBCDIC) and the network encoding
    (ASCII / ISO-8859)
    

Local fix

  • Running the JVM in "ASCII" mode with a different default
    encoding may resolve your issue, but may also cause problems in
    applications that expect normal z/OS EBCDIC processing.
    
    This would require the following three arguments to the JVM to
    change the default encoding, ensure EBCDIC messages, and allow
    EBCDIC input parameters/arguments:
    
     -Dfile.encoding=ISO8859-1
     -Dconsole.encoding=CP1047
     -Xnoargsconversion
    

Problem summary

  • As per JAX specification, the header of the message should be in
    ASCII format and it has to be processed in ASCII encoding. For
    non-zOS platforms, the default encoding is ASCII and it process
    the message properly. For zOS, the default encoding is EBCDIC
    and process the message in EBCDIC as encoding is not explicitly
    specified while processing the message which cause the failure.
    

Problem conclusion

  • This defect will be fixed in:
    6.0.0 SR11
    6.0.1 SR3
    7.0.0 SR3
    .
    JVM is updated to use ASCII encoding explicitly for processing
    message headers in web service.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV14834

  • Reported component name

    JAVA CLASS LIBS

  • Reported component ID

    620700130

  • Reported release

    600

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-02-02

  • Closed date

    2012-04-24

  • Last modified date

    2012-05-14

  • 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

    JAVA CLASS LIBS

  • Fixed component ID

    620700130

Applicable component levels

  • R600 PSY

       UP

  • R700 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Runtimes for Java Technology
Java Class Libraries

Software version:

6.0

Reference #:

IV14834

Modified date:

2012-05-14

Translate my page

Machine Translation

Content navigation