Quantcast
Channel: VMware Communities : All Content - VMware vCenter™
Viewing all articles
Browse latest Browse all 24426

Getting SOAPFaultException while using retrievePropertiesEx( ) method

$
0
0

   Hi All,              

            I have some problem while using retrievePropertiesEx() method to retrieve properties.

            I am getting  the following SOAPFaultException while retrieving properties using PropertyCollector class as:

          retrievePropertiesEx(mor_, pfspec, options)

 

Once this exception starts coming , all the subsequent calls to retrievePropertiesEx() throws the below mentioned SOAPFaultException exception.

              

I know that RetrievePropertiesEx() method is used for a single retrieval operation. So, whenever I need to retrieve properties, I create a new instance of PropertyCollector and then retrieve properties as below.

mor_ = vcs.getVimPort().createPropertyCollector(vcs.getServiceContent().getPropertyCollector());

RetrieveResult rr= vcenter_.getVimPort().retrievePropertiesEx(mor_, pfspec, options);

 

After retrieving properties, I destroy the property collector as:

vcenter_.getVimPort().destroyPropertyCollector(mor_);

 

This exception doesn’t come every time. Once in a while, the exception comes and all subsequent calls to retrievePropertiesEx() throws  this exception. This gets resolved when I manually reset the connection/ restart the VM running this code.

 

The exception says SOAPFaultException : The object has already been deleted or has not been completely created. Does it mean that the object whose properties I am trying to retrieve is already deleted at Vcentre ? The same method retrievePropertiesEx() which retrieved me the properties 5 seconds ago is now throwing the exception. Why is the object getting deleted and why does it work after resetting the connection? Is it problem with creating a PropertyCollector that is throwing me this exception or Is there a connectivity problem to Vcentre that is leading to this problem ?

 

The exception message “The object has already been deleted or has not been completely created” doesn’t give me the clear understanding of the underlying problem. Please let me know the reason for getting this exception and ways to resolve it.

 

Exception Stack:

  1. javax.xml.ws.soap.SOAPFaultException: The object has already been deleted or has not been completely created

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:107)

at $Proxy35.retrievePropertiesEx(Unknown Source)

at com.alu.lrc.vmware.PropertyCollector.RetrieveProperties(PropertyCollector.java:87)

at com.alu.lrc.vmware.VmwareEntity.retrieveVmwareProperties(VmwareEntity.java:136)

at com.alu.lrc.vmware.VmwareEntity.loadAllProperties(VmwareEntity.java:81)

at com.alu.lrc.vmware.VmwareEntity.getProperty(VmwareEntity.java:144)

at com.alu.lrc.vmware.VmwareEntity.getName(VmwareEntity.java:206)


Viewing all articles
Browse latest Browse all 24426

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>