you are right, in fact there is only one instance that manages more than 200 MB, with Top Consumers Biggest Top-Level Dominator Class Loaders LabelNumber of ObjectsUsed Heap SizeRetained Heap SizeRetained Heap, % java.net.FactoryURLClassLoader @ 0xed503040 2.437 89.384 212.569.400 89,81% org.apache.catalina.loader.ParallelWebappClassLoader @ 0xecc5f4a0 3.212 121.744 11.547.920 4,88% <system class loader> 21.740 938.712 9.264.456 3,91% java.net.URLClassLoader @ 0xecc27b48
519 18.784 2.762.008 1,17% - Total: 4 entries 27.908 1.168.624 236.143.784 I am trying to gather further info but eclipse MAT is sometimes a bit confuse El lun., 17 sept. 2018 a las 14:18, Karl Wright (<[email protected]>) escribió: > How many instances does MAT show for ElasticSearchConnection? > > A "leak suspect" is the class whose number of instances is the largest. It > doesn't mean there's an actual memory leak. > > Karl > > > On Mon, Sep 17, 2018 at 7:49 AM Gustavo Beneitez < > [email protected]> > wrote: > > > Hi Karl, > > > > I reviewed the UI and there are a total of > > ElasticSearch 100 > > Seems not so many connections... > > > > > > > > El lun., 17 sept. 2018 a las 12:56, Karl Wright (<[email protected]>) > > escribió: > > > > > Hi Gustavo, > > > > > > Connector instances are pooled in general, so once a connector instance > > is > > > created it is kept around. The number of instances will max out at the > > > number of connections you allow in the UI when defining the connection. > > > How many did you allocate? > > > > > > Karl > > > > > > > > > On Mon, Sep 17, 2018 at 6:23 AM Gustavo Beneitez < > > > [email protected]> > > > wrote: > > > > > > > Hi there, > > > > > > > > I was indexing in production several intranet websites and I realized > > the > > > > performance was becoming poor (no tomcat restart for two weeks). > > > > > > > > After a few thoughts about what is going on I decided to create a > dump > > > > file and review it with eclipse MAT and I observed that the class > > > > > > > > Leak Suspects > > > > > > > > > > *org.apache.manifoldcf.agents.output.elasticsearch.ElasticSearchConnection* > > > > > > > > had a lot of instances and was growing up and never released. Do you > > have > > > > any issue related to Elastic? Maybe there is something related to our > > > > version (2.4.6) of Elastic. > > > > > > > > I also have attached the MAT report. We have all components "by > > default", > > > > i.e. neither no customization of any component nor any new one > created. > > > > > > > > Thanks in advance. > > > > > > > > > >
