IBM Support

PM18694: A JAX-RPC APPLICATION MIGHT RECEIVE A NULL JAVAX.ACTIVATION.DATAHANDLER PARAMETER.

Fixes are available

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
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
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
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
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
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
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.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
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

  • Consider a JAX-RPC application that receives a SOAP message
    with an attachment that looks like the following:
    
    ------=_Part_0_1680106532.1279147179453
    Content-Type: text/xml; charset=UTF-8
    Content-Transfer-Encoding: binary
    Content-Id:
    <521419728031.1279147179453.IBM.WEBSERVICES@myhost>
    
    <soapenv:Envelope
    xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <soapenv:Body>
    <p146:sayHello
    xmlns:p146="http://com.example.ibm/"/>
    </soapenv:Body>
    </soapenv:Envelope>
    ------=_Part_0_1680106532.1279147179453
    Content-Type: application/octet-stream
    Content-Transfer-Encoding: binary
    Content-Id:
    <dh=5173860199.1279147179437.IBM.WEBSERVICES@myhost>
    ...
    
    And the application's service endpoint interface looks
    like this:
    
    public interface HelloWorld extends java.rmi.Remote {
    public int sayHello(javax.activation.DataHandler dh)
    throws java.rmi.RemoteException;
    }
    
    The application might receive null for the
    javax.activation.DataHandler parameter named "dh". This could
    cause a NullPointerException error to occur in the application
    class.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users and developers of IBM WebSphere       *
    *                  Application Server JAX-RPC applications     *
    *                  receiving SOAP messages with attachments
    ****************************************************************
    * PROBLEM DESCRIPTION: A JAX-RPC application might receive a   *
    *                      null javax.activation.DataHandler       *
    *                      parameter.                              *
    ****************************************************************
    * RECOMMENDATION:  Install a fixpack that includes this APAR.  *
    ****************************************************************
    Consider a JAX-RPC application that receives a SOAP message
    with attachment that looks like the following:
    
    ------=_Part_0_1680106532.1279147179453
    Content-Type: text/xml; charset=UTF-8
    Content-Transfer-Encoding: binary
    Content-Id:
       <521419728031.1279147179453.IBM.WEBSERVICES@myhost>
    
    <soapenv:Envelope
    xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
             <soapenv:Body>
                <p146:sayHello
    xmlns:p146="http://com.example.ibm/"/>
             </soapenv:Body>
          </soapenv:Envelope>
    ------=_Part_0_1680106532.1279147179453
    Content-Type: application/octet-stream
    Content-Transfer-Encoding: binary
    Content-Id:
       <dh=5173860199.1279147179437.IBM.WEBSERVICES@myhost>
    ...
    
    And the application's service endpoint interface looks
    like this:
    
    public interface HelloWorld extends java.rmi.Remote {
        public int sayHello(javax.activation.DataHandler dh)
    throws java.rmi.RemoteException;
    }
    
    The application might receive null for the
    javax.activation.DataHandler parameter named "dh". This could
    cause a NullPointerException error to occur in the application
    class.
    
    For example, this NullPointerException error might occur on a
    JAX-RPC service that is the recipient of such a message:
    
    [10/06/16 13:59:19:312 JST] 0000002c SystemErr     R
    java.lang.NullPointerException
    [10/06/16 13:59:19:312 JST] 0000002c SystemErr     R    at
    com.example.ibm.HelloWorldImpl.sayHello(HelloWorldImpl.java:13)
    [10/06/16 13:59:19:312 JST] 0000002c SystemErr     R    at
    sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [10/06/16 13:59:19:312 JST] 0000002c SystemErr     R    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
    Impl.java:79)
    [10/06/16 13:59:19:312 JST] 0000002c SystemErr     R    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
    AccessorImpl.java:43)
    [10/06/16 13:59:19:312 JST] 0000002c SystemErr     R    at
    java.lang.reflect.Method.invoke(Method.java:618)
    [10/06/16 13:59:19:312 JST] 0000002c SystemErr     R    at
    com.ibm.ws.webservices.engine.dispatchers.java.JavaDispatcher.in
    vokeMethod(JavaDispatcher.java:178)
    [10/06/16 13:59:19:312 JST] 0000002c SystemErr     R    at
    com.ibm.ws.webservices.engine.dispatchers.java.JavaDispatcher.in
    vokeOperation(JavaDispatcher.java:141)
    [10/06/16 13:59:19:312 JST] 0000002c SystemErr     R    at
    com.ibm.ws.webservices.engine.dispatchers.SoapRPCProcessor.proce
    ssRequestResponse(SoapRPCProcessor.java:481)
    [10/06/16 13:59:19:312 JST] 0000002c SystemErr     R    at
    com.ibm.ws.webservices.engine.dispatchers.SoapRPCProcessor.proce
    ssMessage(SoapRPCProcessor.java:427)
    [10/06/16 13:59:19:312 JST] 0000002c SystemErr     R    at
    com.ibm.ws.webservices.engine.dispatchers.BasicDispatcher.proces
    sMessage(BasicDispatcher.java:134)
    ...
    
    The NullPointerException occurs because application class
    com.example.ibm.HelloWorldImpl tries to invoke a method on the
    incoming javax.activation.DataHandler parameter, which is null:
    
        public int sayHello(javax.activation.DataHandler dh)
    throws java.rmi.RemoteException {
         System.out.println(dh.getName());
         return -3;
        }
    
    The NullPointerException error would result in this service
    sending a SOAP Fault to the client.
    
    Note, however, that if the client is the recipient of the
    message with attachment, and the JAX-RPC client code tries to
    invoke a method on the null DataHandler, the
    NullPointerException can occur there, too.
    

Problem conclusion

  • The JAX-RPC runtime was corrected to process the
    incoming javax.activation.DataHandler parameter and pass it
    on to the receiving application method.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 6.1.0.35 and 7.0.0.13.  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

    PM18694

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    61I

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-07-19

  • Closed date

    2010-07-29

  • Last modified date

    2010-07-29

  • 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 APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 6.1

Reference #: PM18694

Modified date: 29 July 2010