IBM Support

PM18738: JAX-RPC WEB SERVICE HANDLER IS NOT INVOKED.

Fixes are available

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

  • After upgrading WebSphere Application Server to v6.1.0.29,
    JAX-RPC handlers configured in a web service Dynamic
    Interface Invocation (DII) client do not get invoked.
    
    This problem does not result in a specific exception.  Rather,
    the application might encounter unpredictable behavior which is
    caused by the JAX-RPC handler not getting invoked.
    

Local fix

  • Instead of doing a no argument call to Service.createCall,
    try using this:
    
    Service.createCall(portTypeName, operationQName)
    
    Do not call Call.setPortTypeName(portType), or
    Call.setOperationName(operationQName).
    
    Here's an example of the modified code in WebserviceClientCall:
     ServiceFactory sf = ServiceFactory.newInstance();
     QName serviceQname = new QName(targetNamespace, serviceName);
     QName portTypeName = new QName(targetNamespace,portType);
     QName operationQName = new QName(targetNamespace,
       operationName);
     javax.xml.rpc.Service service =
       (javax.xml.rpc.Service)sf.createService(serviceQname);
     javax.xml.rpc.Call call =
       service.createCall(portTypeName,operationQName);
     //Don't need to do this -> call.setOperationName(new
     //   QName(targetNamespace, operationName));
     call.setProperty(Call.OPERATION_STYLE_PROPERTY,
       operationStyle);
     call.setProperty(Call.ENCODINGSTYLE_URI_PROPERTY, "");
     call.setProperty(Call.SOAPACTION_URI_PROPERTY,targetNamespace);
     call.setProperty(Call.SOAPACTION_USE_PROPERTY,
       Boolean.TRUE);
     call.setTargetEndpointAddress(endPointAddress);
     //Don't need to do this -> call.setPortTypeName(new
     //   QName (targetNamespace,portType));
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V6.1 and V7.0 and JAX-RPC DII        *
    *                  clients.                                    *
    *                                                              *
    *                                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: JAX-RPC Web service handlers may not    *
    *                      get invoked for DII clients after       *
    *                      upgrading to WebSphere Application      *
    *                      Server V6.1.0.29.                       *
    ****************************************************************
    * RECOMMENDATION:  Install a fixpack containing this APAR.     *
    ****************************************************************
    After upgrading WebSphere Application Server to v6.1.0.29,
    JAX-RPC handlers configured in a web service Dynamic
    Interface Invocation (DII) client do not get invoked.
    
    This may happen if the DII client has all of the following
    characteristics:
    a) It does not specify a WSDL file
    b) It does not specify a portName on the call to
    Service.createCall()
    c) It uses Call.setPortTypeName to set the portName
    d) It configures JAX-RPC handlers in the handlerChain using
    the same portName set in c) above.
    
    Here is an example of the failing client:
    
    javax.xml.rpc.Service service =
    (javax.xml.rpc.Service)sf.createService(serviceQname);
    javax.xml.rpc.Call call = service.createCall();
    call.setOperationName(operationName);
    call.setPortTypeName(portName);
    HandlerRegistry hr=service.getHandlerRegistry();
    List<HandlerInfo> list = new ArrayList<HandlerInfo>();
    HandlerInfo hi=new HandlerInfo(SampleHandler.class,null,null);
    list.add(hi);
    hr.setHandlerChain(portName, list);
    call.invoke(input);
    
    In this case, the SampleHandler would not get invoked on the
    client.
    
    This problem does not result in a specific exception.  Rather,
    the application might encounter unpredictable behavior which is
    caused by the JAX-RPC handler not getting invoked.
    

Problem conclusion

  • The failure in this case is happening because of the use of
    Call.setPortTypeName to set the portName.  Under most
    circumstances the portName is set when the Call object is
    created, either by passing it to Service.callCreate or by
    deriving it from the WSDL.
    
    Prior to V6.1.0.29, Call.setPortTypeName could be used to set
    or reset the portName after the Call object was created.  APAR
    PK93531 removed this capability on the grounds that the
    portTypeName and portName are actually two different things
    and should not be interchanged.  However, this has caused some
    compatibility issues.
    
    The fix is to allow Call.setPortTypeName to be used to set the
    portName only if the portName has not already been derived
    from the WSDL or passed as a parameter to Service.createCall.
    If the portName is already established, setPortTypeName will
    not overwrite it.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.15 and 6.1.0.35.  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

    PM18738

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    61A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-07-19

  • Closed date

    2010-09-07

  • Last modified date

    2010-09-07

  • 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

  • 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 #: PM18738

Modified date: 07 September 2010