[
https://issues.apache.org/jira/browse/SSHD-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16667831#comment-16667831
]
jpalacios commented on SSHD-854:
--------------------------------
[~lgoldstein],
Thanks for the suggestion. However this heap dump came from an incident one of
our customers experienced in their production instance so we need to be careful
with what we test. Asking them to invest time in upgrading the system is
certainly an option but we'd like to be able to explain why we believe the root
cause would be removed. Upgrading in a test environment is unlikely to
reproduce the issue since it won't see the same kind of sustained load. Do you
have a theory as to how the system could've gotten into this state using SSHD
{{1.7.0}}? What change specifically in the 2.x releases would resolve it?
Cheers
Juan Palacios
> 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)
