axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "pravin patil (JIRA)" <axis-...@ws.apache.org>
Subject [jira] Updated: (AXIS-2774) AXIS 1.4 Issue with Vmware for German char set .
Date Mon, 02 Feb 2009 15:19:59 GMT

     [ https://issues.apache.org/jira/browse/AXIS-2774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

pravin patil updated AXIS-2774:
-------------------------------

    Attachment: AXIS-2774.zip

Please find attached zip for setup detail, AXIS conf file (e.g client-config.wsdd) and log.

> AXIS 1.4 Issue with Vmware for German char set .
> ------------------------------------------------
>
>                 Key: AXIS-2774
>                 URL: https://issues.apache.org/jira/browse/AXIS-2774
>             Project: Axis
>          Issue Type: Bug
>          Components: Serialization/Deserialization
>    Affects Versions: 1.4
>         Environment: OS: german , Windows 2003
> Software platform: Java, VMware web service api
> Setup: 
> 1. ASM (My produce) is installed on top of NSM, 
> 2. ASM Proxy service gathers data from VMware Virtual center service.
> 3. every ASM/NSM connect goes ONLY via Firewall to the remote DSM and then to the VCS
Server
> Hints:
> - Users had only access via Firewall to the Portal and Citrix ( from NSM () Perspective).
> - every NSM connect goes ONLY via Firewall to the remote DSM and then to the VCS Server
> - Microsoft Hot Fixes are deliver via WSUS from the Windows Security Team
> More info:
> 1. Is the problem reproducible? - YES
> 2. VirtualCenter Version - 2.5 Build 84767
> 3. Host Version - ESX3.0.2 Build 95415/61618 AND ESX 3.0.1Build 60875          
> 4. VI SDK Version - 2.5
> 5. How many Host Systems for each ESX Server version are you running?: 15 (esx 3.0.2
servers) and 87 VMs
> 6. Toolkit Used: AXIS 1.4
>            Reporter: pravin patil
>            Priority: Critical
>             Fix For: 1.4
>
>         Attachments: AXIS-2774.zip
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message