satish123REUGHE's Posts

Hi All, We getting the above error while development of Remote Plugin, the plugin is getting registered successfully, But getting erro in the vimService.getVimPort() call. I have attached the content of Manifest.mf file too Could anyone please help ? com.sun.xml.ws.model.RuntimeModelerException: A WebService annotation is not present on class: com.vmware.vim25.VimPortType at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:239) at com.sun.xml.ws.db.DatabindingImpl.<init>(DatabindingImpl.java:70) at com.sun.xml.ws.db.DatabindingProviderImpl.create(DatabindingProviderImpl.java:44) at com.sun.xml.ws.db.DatabindingProviderImpl.create(DatabindingProviderImpl.java:28) at com.sun.xml.ws.db.DatabindingFactoryImpl.createRuntime(DatabindingFactoryImpl.java:90) at com.sun.xml.ws.client.WSServiceDelegate.buildRuntimeModel(WSServiceDelegate.java:852) at com.sun.xml.ws.client.WSServiceDelegate.createSEIPortInfo(WSServiceDelegate.java:869) at com.sun.xml.ws.client.WSServiceDelegate.addSEI(WSServiceDelegate.java:832) at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:421) at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:390) at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:372) at javax.xml.ws.Service.getPort(Service.java:119) at com.vmware.vim25.VimService.getVimPort   Content of Manifest.mf file: Manifest-Version: 1.0 Export-Package: com.vmware.vim25;uses:="javax.jws,javax.xml.bind,javax.xml.bind.annotation,javax.xml.datatype,javax.xml.namespace,javax.xml.ws" Bundle-ManifestVersion: 2 Bundle-Name: html-sample-ui Bundle-SymbolicName: com.vmware.samples.htmlsample.ui Bundle-Version: 1.0.0 Bundle-Vendor: VMware Web-ContextPath: ui/html-sample Import-Package: com.vmware.samples.htmlsample.controllers;version="1.0.0", com.vmware.samples.htmlsample.services;version="1.0.0", com.vmware.vise.security;version="0", org.eclipse.virgo.web.dm;version="3.6.0", org.springframework.web.servlet;version="4.2.9", org.springframework.web.servlet.config;version="4.2.9", javax.jws,javax.xml.bind,javax.xml.bind.annotation,javax.xml.datatype,javax.xml.namespace,javax.xml.ws     Regards, Satish

In the remote plugin workflow, we are able to clone the session and get the UserSession Object, however looks like there is no way to get the sessionId making use of the session. Please share if there is a way to get the session ID.

One of our cusotmer has reported two issues related to vmware API on same vcenter and hence putting the details of both issues : Issue 1 (Wrapper timeout issue): Customer reported that our product's backup is failing with wrapper timeout issue and when we deep dived into it, it was observed that "find_entity_views( view_type => 'Datacenter' )" API is not returing any response and hence the application is throwing timeout issue. Important point to notice here is when we moved a datastore to another datacenter, the backup was successful. But as customer has huge environment they are not willing to move their datastores to another datacenter. Hence we need your help to look into this from API side and want to know what may be the possible reason for failures on a particular datacenter. Issue 2(Java Heap Issue): Customer reported that the backup is failing with Java Heap issue(OutOfMemmory error) and when we looked into it, it was observed that when tapplication tries to get details of virtual machines through API "find_entity_views( view_type => 'VirtualMachine')", it fails with OutOfMemory issue. This issue is occurring on all the datastores of a particular datacenter. The number of virtual machines are 6000+ but the same configuration was working fine till the customer observed this issue. We suspect the response returned by this API might have some garbage/irrelevant data due to which it is not able to store the API response now and end up with outOfMemory issue. Kindly note that both the issues started occurring from a particular day and customer denied any configuration changes on that day. Prior to that everything was working as expected.