You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Goncharuk (JIRA)" <ji...@apache.org> on 2019/06/17 07:32:00 UTC
[jira] [Created] (IGNITE-11930) TcpDiscoverySpi does not close
bound server socket if discovery thread did not start
Alexey Goncharuk created IGNITE-11930:
-----------------------------------------
Summary: 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
Fix For: 2.8
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)