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

AXIS 1.4 Issue with Vmware for German char set .

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Critical
    • Resolution: Unresolved
    • Affects Version/s: 1.4
    • Fix Version/s: None
    • Labels:
      None
    • Environment:

      Description

      Problem is occurring while getting information related to VM using VI SDK on German Client.

      There is axisfault message in the attached log file:
      2008-10-31 15:05:35,813 [main] FATAL com.ca.proxyservice.connectionmanager.CAVCProxy - startup: Could not initialize CAVCProxy
      AxisFault
      faultCode:

      {http://schemas.xmlsoap.org/soap/envelope/}

      Server.userException
      faultSubcode:
      faultString: org.xml.sax.SAXParseException: Invalid byte 2 of 3-byte UTF-8 s
      equence.
      faultActor:
      faultNode:
      faultDetail:

      {http://xml.apache.org/axis/}

      stackTrace:org.xml.sax.SAXParseException:
      Invalid byte 2 of 3-byte UTF-8 sequence.
      at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createS
      AXParseException(Unknown Source)

      To investigate the issue further we created a client-config.wsdd file which will dump the SOAP Messages. But our proxy service started working when we use the client-config.wsdd file.

      If we remove the Axis config file then proxy service fails and we were getting the same exception as mentioned above.

      Attached herewith the vc proxy log and client-config.wsdd file for more investigation.
      Problem Assumption: It seems there is some localization exception in AXIS1.4 while parsing the soap response returned by Virtual Center API.

        Attachments

        1. AXIS-2774.zip
          272 kB
          pravin patil

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              pravin pravin patil
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:

                Time Tracking

                Estimated:
                Original Estimate - 168h
                168h
                Remaining:
                Remaining Estimate - 168h
                168h
                Logged:
                Time Spent - Not Specified
                Not Specified