Le 12/10/2018 à 22:14, Pankaj Rathod a écrit : > Hi Emmanuel, > > I could finally generate dumps in hprof format. I have shared you heapdumps > (java.2018.10.01-11.07.22.hprof) in same folder where earlier I had sent > PHD format dumps. > > This heapdump is for very small heap memory size. But you can notice in > this dump that there are around 1818 objects of NioSocketSession class. > > In our system environment (and in our PHD dumps), we see around 80000 > objects of NioSocketSession class, which combinely occupying around 95% of > heap memory. This is the leak suspect as per our PHD dump analysis. The > heap analyzer tool mentions One instance of NioSocketAcceptor occupies 95% > memory. > > Please ignore the memory occupied by ACLTableGenerator class in heapdumps. > It has fixed size. It is a custom class developed for our need.
Hi ! I just quickly checked the provided hprof file, which has 2469 NioSession instances. What it means is that many LDAP conections have been initiated, and never dropped. At this point, I can see 2 scenario : - the clients start a connection, and never close it - the clients start a connection, close it, but the server never ditch it In the second case, we should check wht happens when the client close the connection. The NioSession object should be discarded. The first scenario is more annoying : it's perfectly possible that the client never close the connection, so the serve rkeep the NioSession forever. We should have a timeout for this case, which automatically closes the connection after a configured innactivity timeout. In your test, can you tell me if your client is closing the connection, and how ? Thanks ! -- Emmanuel Lecharny Symas.com directory.apache.org
pEpkey.asc
Description: application/pgp-keys
