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

Ignite TC Bot commented on IGNITE-11930:
----------------------------------------

{panel:title=--> Run :: All: No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4138760&buildTypeId=IgniteTests24Java8_RunAll]

> 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: 10m
>  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)

Reply via email to