Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
4.5.0
-
None
-
Security Level: Public (Anyone can view this level - this is the default.)
-
None
-
Latest build from 4.5
Description
[VMWare]javax.xml.ws.soap.SOAPFaultException during system vms start
Steps to Reproduce:
===============
1.Create CS 4.5 setup using vmware cluster
2.Wait for the system vms to come up
Observations:
==========
During system vms start up we see lot of javax.xml.ws.soap.SOAPFaultExceptions in the MS log file
2014-10-21 21:17:28,104 WARN [c.c.h.v.m.HttpNfcLeaseMO] (Thread-29:null) Unexpected exception
javax.xml.ws.soap.SOAPFaultException: A specified parameter was not correct.
percent
at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178)
at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:119)
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:108)
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78)
at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:129)
at $Proxy413.httpNfcLeaseProgress(Unknown Source)
at com.cloud.hypervisor.vmware.mo.HttpNfcLeaseMO.updateLeaseProgress(HttpNfcLeaseMO.java:104)
at com.cloud.hypervisor.vmware.mo.HttpNfcLeaseMO$ProgressReporter.run(HttpNfcLeaseMO.java:163)
But these exceptions disappear when the system vms are up and running.