[ https://issues.apache.org/jira/browse/IGNITE-13226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17153072#comment-17153072 ]
Sergey Stronchinskiy commented on IGNITE-13226: ----------------------------------------------- [~ptupitsyn] looks fine to me! > .NET: Thin Client Compute leaks ClientNotificationHandler instances > ------------------------------------------------------------------- > > Key: IGNITE-13226 > URL: https://issues.apache.org/jira/browse/IGNITE-13226 > Project: Ignite > Issue Type: Bug > Components: platforms > Affects Versions: 2.9 > Reporter: Pavel Tupitsyn > Assignee: Pavel Tupitsyn > Priority: Critical > Labels: .NET > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > In multithreaded thin client compute scenarios there is a possibility for > ClientNotificationHandler leak: handlers remain in > ClientSocket._notificationListeners even after corresponding tasks have > completed. > To reproduce, add the following code at the end of > ComputeClientTests.TestExecuteJavaTaskAsyncMultithreaded: > {code} > var failoverSocket = > TestUtils.GetPrivateField<ClientFailoverSocket>(client, "_socket"); > var socket = > TestUtils.GetPrivateField<ClientSocket>(failoverSocket, "_socket"); > var listeners = TestUtils.GetPrivateField<ICollection>(socket, > "_notificationListeners"); > Assert.IsEmpty(listeners); > {code} -- This message was sent by Atlassian Jira (v8.3.4#803005)