IBM Support

PM25697: A "WSWS3031E: ERROR: SERIALIZATION CANNOT OCCUR FOR ..." ERROR MAY OCCUR FOR A JAX-RPC CLIENT.

Fixes are available

6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
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

  • The following error might occur for a JAX-RPC client:
    
    java.io.IOException: WSWS3701E: Error: An exception was
    encountered.  Use the wsdeploy command to deploy your
    application.  The exception is java.io.IOException: WSWS3031E:
    Error: Serialization cannot occur for
    com.example.HelloGreeting  There are no registered
    type mappings. Debug deploy artifact build numbers={pre-WAS 6.0
    build}
     at
    com.ibm.ws.webservices.engine.WebServicesFault.makeFault(WebServ
    icesFault.java:282)
     at
    com.ibm.ws.webservices.engine.SOAPPart.writeTo(SOAPPart.java:925
    )
     at
    com.ibm.ws.webservices.engine.SOAPPart.writeTo(SOAPPart.java:840
    )
     at
    com.ibm.ws.webservices.engine.SOAPPart._getWebServicesInputSourc
    e(SOAPPart.java:974)
     at
    com.ibm.ws.webservices.engine.SOAPPart.getString(SOAPPart.java:5
    83)
     at
    com.ibm.ws.webservices.engine.client.Connection.invoke(Connectio
    n.java:666)
     at
    com.ibm.ws.webservices.engine.client.Connection.invoke(Connectio
    n.java:500)
     at
    com.ibm.ws.webservices.engine.client.Call.invoke(Call.java:1772)
     at
    com.ibm.ws.webservices.engine.client.Call.invoke(Call.java:1709)
     at
    com.ibm.ws.webservices.multiprotocol.AgnosticCall.invoke(Agnosti
    cCall.java:237)
     at
    com.ibm.ws.webservices.multiprotocol.base.DefaultlInvocationHand
    ler.invokeOperation(DefaultlInvocationHandler.java:203)
     at
    com.ibm.ws.webservices.multiprotocol.models.ModelInvocationHandl
    er.invoke(ModelInvocationHandler.java:88)
    ...
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Developers of IBM WebSphere Application     *
    *                  Server V6.1 and V7.0 JAX-RPC clients.       *
    ****************************************************************
    * PROBLEM DESCRIPTION: A "WSWS3031E: Error: Serialization      *
    *                      cannot occur for ..." error might       *
    *                      occur for a JAX-RPC client.             *
    ****************************************************************
    * RECOMMENDATION:  Install a fix pack that includes this APAR. *
    ****************************************************************
    The following error might occur for a JAX-RPC client:
    
    [10/28/10 10:01:41:788 EDT] 00000037 Call          1
    com.ibm.ws.webservices.engine.client.Call getWSDLQuery Call::
    WSDLQuery failed, exception ignored, processing continues.
    ../types/zip/ZipCode.xsd (No such file or directory)
    
    java.io.FileNotFoundException: ../aaaaa/bbb/ccccccc.xsd
    (No such file or directory)
     at java.io.FileInputStream.<init>(FileInputStream.java:135)
     at java.io.FileInputStream.<init>(FileInputStream.java:95)
     at
    sun.net.www.protocol.file.FileURLConnection.connect(FileURLConne
    ction.java:85)
     at
    sun.net.www.protocol.file.FileURLConnection.getInputStream(FileU
    RLConnection.java:176)
     at
    com.ibm.ws.webservices.wsdl.symbolTable.Resolver._makeAbsoluteUR
    L(Resolver.java:534)
     at
    com.ibm.ws.webservices.wsdl.symbolTable.Resolver.setInfoDoc(Reso
    lver.java:614)
     at
    com.ibm.ws.webservices.wsdl.symbolTable.Resolver._resolveXSD(Res
    olver.java:312)
     at
    com.ibm.ws.webservices.wsdl.symbolTable.Resolver.resolveXSDImpor
    t(Resolver.java:234)
    ...
     at
    com.ibm.ws.webservices.engine.client.Call.invokeWSDLQueryParse(C
    all.java:2590)
     at
    com.ibm.ws.webservices.engine.client.Call.getWSDLQuery(Call.java
    :2693)
     at
    com.ibm.ws.webservices.engine.client.Call.getWSDLQueryOperationD
    esc(Call.java:2780)
     at
    com.ibm.ws.webservices.engine.client.Call.copyOptionsFromWSDLOpe
    ration(Call.java:2847)
     at
    com.ibm.ws.webservices.engine.client.Call.invoke(Call.java:1760)
     at
    com.ibm.ws.webservices.engine.client.Call.invoke(Call.java:1709)
     at
    com.ibm.ws.webservices.multiprotocol.AgnosticCall.invoke(Agnosti
    cCall.java:237)
    ...
    
    Shortly after, problems with serializing the request might
    occur:
    
    java.io.IOException: WSWS3701E: Error: An exception was
    encountered.  Use the wsdeploy command to deploy your
    application.  The exception is java.io.IOException: WSWS3031E:
    Error: Serialization cannot occur for
    com.example.HelloGreeting  There are no registered
    type mappings. Debug deploy artifact build numbers={pre-WAS 6.0
    build}
     at
    com.ibm.ws.webservices.engine.WebServicesFault.makeFault(WebServ
    icesFault.java:282)
     at
    com.ibm.ws.webservices.engine.SOAPPart.writeTo(SOAPPart.java:925
    )
     at
    com.ibm.ws.webservices.engine.SOAPPart.writeTo(SOAPPart.java:840
    )
     at
    com.ibm.ws.webservices.engine.SOAPPart._getWebServicesInputSourc
    e(SOAPPart.java:974)
     at
    com.ibm.ws.webservices.engine.SOAPPart.getString(SOAPPart.java:5
    83)
     at
    com.ibm.ws.webservices.engine.client.Connection.invoke(Connectio
    n.java:666)
     at
    com.ibm.ws.webservices.engine.client.Connection.invoke(Connectio
    n.java:500)
     at
    com.ibm.ws.webservices.engine.client.Call.invoke(Call.java:1772)
     at
    com.ibm.ws.webservices.engine.client.Call.invoke(Call.java:1709)
     at
    com.ibm.ws.webservices.multiprotocol.AgnosticCall.invoke(Agnosti
    cCall.java:237)
     at
    com.ibm.ws.webservices.multiprotocol.base.DefaultlInvocationHand
    ler.invokeOperation(DefaultlInvocationHandler.java:203)
     at
    com.ibm.ws.webservices.multiprotocol.models.ModelInvocationHandl
    er.invoke(ModelInvocationHandler.java:88)
     at $Proxy2.sayHello(Unknown Source)
     at
    com.example.HelloWorldServicePortTypeProxy.
    sayHello(HelloWorldServicePortTypeProxy.java:71)
    ...
    
    This problem happens when the client does the following:
    
    1) Uses the DII model (javax.xml.rpc.Call API), as mentioned
    previously, and
    2) Uses a WSDL that imports or includes a separate schema
    file.
    
    Note that this error is very similar to the one that PM01453
    resolved. However, PM01453 did not take into account all the
    scenarios in which the Call object is created; it only takes
    affect if the Call object was created with the Web service's
    operation name. PM25697 should cover all scenarios of invoking
    the Call API.
    
    This error might also occur for clients not explicitly using
    DII. If the client uses a *Proxy class generated by Rational
    Application Developer to invoke the Web service, and the
    referenced WSDL2Java-generated *Stub class is not included in
    the client application, then the Call API would be invoked,
    and this error might occur.
    

Problem conclusion

  • The JAX-RPC runtime was fixed to resolve the schema file
    imported or included by the parent WSDL file.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 6.1.0.37 and 7.0.0.17.  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

    PM25697

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    61Z

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-11-02

  • Closed date

    2010-12-27

  • Last modified date

    2010-12-27

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

Modified date: 27 December 2010