[jira] [Updated] (CLOUDSTACK-7759) [VMWare]javax.xml.ws.soap.SOAPFaultException during system vms start
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty updated CLOUDSTACK-7759: --- Priority: Major (was: Critical) > [VMWare]javax.xml.ws.soap.SOAPFaultException during system vms start > > > Key: CLOUDSTACK-7759 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7759 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.5.0 > Environment: Latest build from 4.5 >Reporter: Sanjeev N >Assignee: Likitha Shetty > Fix For: 4.5.0 > > Attachments: management-server.rar > > > [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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7759) [VMWare]javax.xml.ws.soap.SOAPFaultException during system vms start
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty updated CLOUDSTACK-7759: --- Fix Version/s: (was: 4.5.0) 4.6.0 > [VMWare]javax.xml.ws.soap.SOAPFaultException during system vms start > > > Key: CLOUDSTACK-7759 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7759 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.5.0 > Environment: Latest build from 4.5 >Reporter: Sanjeev N >Assignee: Likitha Shetty > Fix For: 4.6.0 > > Attachments: management-server.rar > > > [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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7759) [VMWare]javax.xml.ws.soap.SOAPFaultException during system vms start
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjeev N updated CLOUDSTACK-7759: -- Attachment: management-server.rar Attached MS log > [VMWare]javax.xml.ws.soap.SOAPFaultException during system vms start > > > Key: CLOUDSTACK-7759 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7759 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.5.0 > Environment: Latest build from 4.5 >Reporter: Sanjeev N >Priority: Critical > Fix For: 4.5.0 > > Attachments: management-server.rar > > > [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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7759) [VMWare]javax.xml.ws.soap.SOAPFaultException during system vms start
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi updated CLOUDSTACK-7759: --- Assignee: Likitha Shetty > [VMWare]javax.xml.ws.soap.SOAPFaultException during system vms start > > > Key: CLOUDSTACK-7759 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7759 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.5.0 > Environment: Latest build from 4.5 >Reporter: Sanjeev N >Assignee: Likitha Shetty >Priority: Critical > Fix For: 4.5.0 > > Attachments: management-server.rar > > > [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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7759) [VMWare]javax.xml.ws.soap.SOAPFaultException during system vms start
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-7759: Assignee: (was: Likitha Shetty) > [VMWare]javax.xml.ws.soap.SOAPFaultException during system vms start > > > Key: CLOUDSTACK-7759 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7759 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.5.0 > Environment: Latest build from 4.5 >Reporter: Sanjeev N > Attachments: management-server.rar > > > [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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7759) [VMWare]javax.xml.ws.soap.SOAPFaultException during system vms start
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-7759: Fix Version/s: (was: 4.6.0) > [VMWare]javax.xml.ws.soap.SOAPFaultException during system vms start > > > Key: CLOUDSTACK-7759 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7759 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.5.0 > Environment: Latest build from 4.5 >Reporter: Sanjeev N > Attachments: management-server.rar > > > [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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
