You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Igor Sapego (Jira)" <ji...@apache.org> on 2022/04/11 06:18:00 UTC

[jira] [Commented] (IGNITE-16776) Thin 3.0: Potential resource leak on disconnect

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

Igor Sapego commented on IGNITE-16776:
--------------------------------------

[~ptupitsyn] looks good to me. Ship it

> Thin 3.0: Potential resource leak on disconnect
> -----------------------------------------------
>
>                 Key: IGNITE-16776
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16776
>             Project: Ignite
>          Issue Type: Bug
>          Components: thin client
>    Affects Versions: 3.0.0-alpha5
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Critical
>              Labels: ignite-3
>             Fix For: 3.0.0-alpha5
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> *ClientResourceRegistry#clean* is called on connection loss. However, some request handlers may be still active and call *put* after or during *clean*, causing a resource leak. We should use an rw lock to handle this.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)