Is there any limit to the number of PropertyFilter (s) in a PropertyCollector?

[monisiqbal]

Although the PropertyFilter are contained to their respective sessions, is there a limit either per session or per ESX server on the number of PropertyFilters that can be created?

Also, if we create too many filters, can it result in erros in comunicating with the web service?

Below is the exception we are getting (we are using visdk), and the troublesome thing that we found incorrect in our code was that we weren't deleting the created filters, and kept on creating and using new ones.

[Thread-99-vmbigboy1-1]: 24 Feb 2011 22:25:47,016 ERROR [ManagedObjectWatcher]:103 - Error while getting updates.

java.rmi.RemoteException: VI SDK invoke exception:org.dom4j.DocumentException: null Nested exception: null

at com.vmware.vim25.ws.WSClient.invoke(WSClient.java:181)

at com.vmware.vim25.ws.WSClient.invoke(WSClient.java:123)

at com.vmware.vim25.ws.VimStub.checkForUpdates(VimStub.java:84)

Thanks,
Monis

[Steve_Jin]

Hi Monis,

I am not aware of any hard limit on the PropertyFilter. However, just as you guessed too many P.F. may overload the server and cause trouble in the end. It's a good practice to remove whatever P.F. no long in use.

From your call stack, I think you use caching framework in the open source vi java API. I would like to see how you use the framework. Please bring the discussion to the vijava forum http://vijava.sf.net

Steve, Author of VMware VI and vSphere SDK, http://www.doublecloud.org