ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Goncharuk (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (IGNITE-11930) TcpDiscoverySpi does not close bound server socket if discovery thread did not start
Date Mon, 17 Jun 2019 14:55:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-11930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alexey Goncharuk resolved IGNITE-11930.
---------------------------------------
    Resolution: Fixed

> TcpDiscoverySpi does not close bound server socket if discovery thread did not start
> ------------------------------------------------------------------------------------
>
>                 Key: IGNITE-11930
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11930
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 2.7
>            Reporter: Alexey Goncharuk
>            Assignee: Alexey Goncharuk
>            Priority: Major
>             Fix For: 2.8
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> See {{ServerImpl.spiStop0(boolean)}}. If the worker did not start, {{U.cancel()}} has
no effect because runner field is not initialized, and server socket is closed in {{onInterrupted()}}
method, which is called from the {{interrupt()}} method on the worker thread.
> This results in the server socket not being closed and may lead to tests hang, for example,
in .NET tests.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message