Uploaded image for project: 'Axis'
  1. Axis
  2. AXIS-2814

could not find deserializer for type

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.1
    • Fix Version/s: None
    • Labels:
      None
    • Environment:
      Linux, JDK 5

      Description

      Sometimes, on hyperthreaded production system, the result of WS can produce exception because the deserializer is null. If the following exception occurs, all folllowing deserailizations will failed.
      When we launch a new client to restart the failed WS, the result will be OK.

      This is the stack.
      13:58:11,647 ERROR [org.apache.axis.client.Call] Exception: org.xml.sax.SAXException: Deserializing parameter 'result': could not find deserializer for type

      {http://myhost/types}

      Xxxx[..]
      at org.apache.axis.message.RPCHandler.onStartChild(RPCHandler.java:302)
      at org.apache.axis.encoding.DeserializationContextImpl.startElement(DeserializationContextImpl.java:963)
      at org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:198)
      at org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:722)
      at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:233)
      at org.apache.axis.message.RPCElement.getParams(RPCElement.java:347)
      at org.apache.axis.client.Call.invoke(Call.java:2272)
      at org.apache.axis.client.Call.invoke(Call.java:2171)
      at org.apache.axis.client.Call.invoke(Call.java:1691)

      Do you know any fix made after 1.1 release related with this issue ?

      Regards

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              gbt GBT
            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: