mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DIRMINA-1096) Massive object graph in NioSocketSession
Date Fri, 26 Oct 2018 02:17:00 GMT

    [ https://issues.apache.org/jira/browse/DIRMINA-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664549#comment-16664549
] 

Emmanuel Lecharny commented on DIRMINA-1096:
--------------------------------------------

Ok, thanks for the clarification. At this point, I would suggest we switch the ticket to {{SSHD}},
the {{CachingPublicKeyAuthenticator}} class belonging to this project, not to {{MINA}} per
se.

> Massive object graph in NioSocketSession
> ----------------------------------------
>
>                 Key: DIRMINA-1096
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-1096
>             Project: MINA
>          Issue Type: Bug
>    Affects Versions: 2.0.16
>            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)

Mime
View raw message