What would be the impact if we not destroy the IData cursor

if not destroyed then heapdumps ll get formed

tomasidn, do you mean that, if IDataCursor will not be destroyed then sometime somewhere it will cause java heap size issue ..

Garbage collector will take care

srinik, without destroying the IDataCursor, how the eligible object (instance of IDataCursor) will become reachable object for garbage collector?

very true. ..fornation of these heapsumps results in out of memory exception ..we faced this kind of problem..very recently we closed idatacursor .now heapdumps issue is reduced to large extent..

So, did u checked or did any change to server.sh file config data --> dataDump OutOfMemory=False and increased the heapsize ?

no..we just closed idatacursor and vector array for all the javaservers....bcz that was. the one od the cauae forheapdump..bcz increaasing heapsize is. not a ideal choice all the times..if datasize is lsrge then we can go for that.....

Yes, we also approaching the same .. Thanks !

its ok dear