[ https://issues.apache.org/jira/browse/SSHD-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16671949#comment-16671949 ]
Goldstein Lyor commented on SSHD-854: ------------------------------------- {quote} It's worth noting that the changes you've made to use session attributes instead of a map to store/retrieve the cached value, would solve the problem I'm describing. When do you think we can expect those changes to be released? {quote} I believe when we release 2.2 - some time in Q1 2019 (unless there is an urgent need to release before that) > Massive object graph in NioSocketSession > ---------------------------------------- > > Key: SSHD-854 > URL: https://issues.apache.org/jira/browse/SSHD-854 > Project: MINA SSHD > Issue Type: Bug > Reporter: jpalacios > Priority: Major > > I'm looking at a heap dump from one of our customers where the retained heap > size for some {{NioSocketSession}} instances is almost 1GB. > From the looks of the dump MINA has created a massive object graph where: > {code} > NioSocketSession -> SelectionKeyImpl -> EpollSelectorImpl -> HashMap -> > SelectionKeyImpl -> NioSocketSession -> ... > {code} > From the looks of the obeject IDs these are not loops > Each individual object is not large by itself but at the top of the graph the > accumulated retained size is enough to produce an OOME > Could you help me understand how MINA can produce such a massive object > graph? Should MINA apply any defense mechanism to prevent this?? -- This message was sent by Atlassian JIRA (v7.6.3#76005)