Alexander B commented on DIRMINA-1081:

Hi guys,

I found the time to check all information. I am not sure where this problem was 
exactly. After some refactoring and the implementation of the WriteFuture 
requests it works and we do not receive this problem again. I am gonna close 
this issue. Thanks a lot.

> Increasing number of ConcurrentLinkedQueue$Node objects
> -------------------------------------------------------
>                 Key: DIRMINA-1081
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-1081
>             Project: MINA
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.16, 2.0.17
>            Reporter: Alexander B
>            Priority: Major
>         Attachments: heap.png, linkedqueuenodes.png, recorded live 
> allocations.png
> In a few issues i read, that some users detect a hugh number of 
> ConcurrentLinkedQueue$Node objects, which are actually not collected by GC. I 
> dont know if this behaviour is still an open bug, so i opened this new issue.
> Attached are two screenshot made by JProfiler. It seems, that the broadcast 
> method references these objects and does not deallocate them.
> In my point of view this behaviour was getting better by using version 2.0.17 
> instead of 2.0.16, but this behaviour still exists.
> PS:  I am using Java 1.8.0_161b12 64bit

This message was sent by Atlassian JIRA

Reply via email to