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

Vladimir Steshin commented on IGNITE-21165:
-------------------------------------------

[~ptupitsyn], could you take a look please? The timeouts have gone.

> .NET platform test timeouts after ClientServerCompatibilityTest
> ---------------------------------------------------------------
>
>                 Key: IGNITE-21165
>                 URL: https://issues.apache.org/jira/browse/IGNITE-21165
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Vladimir Steshin
>            Priority: Major
>              Labels: ise
>         Attachments: 
> Ignite_Tests_2.x_JDK_8_11_Platform_.NET_Core_Linux_39429.log.zip
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> There are many timeouted test runs in the .NET suite. Example:
> https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformNetCoreLinux/7678070
> {code:java}
> The build Ignite Tests 2.x (JDK 8/11)::Platform .NET (Core Linux) #39429 
> {buildId=7678070} has been running for more than 40 minutes. Terminating...
> {code}
> Looks like only port 47500 is requested while server node started on another. 
> Probably a previous test didn't release the port yet.
> {code:java}
> Successfully bound communication NIO server to TCP port [port=47101, 
> locHost=/127.0.0.1, selectorsCnt=4, selectorSpins=0, pairedConn=false]
> {code}
> {code:java}
> Failed to connect to any address from IP finder (make sure IP finder 
> addresses are correct and firewalls are disabled on all host machines): 
> [/127.0.0.1:47500]
> {code}
> It looks like this issue happens on JDK8 only. And only on Linux. 
> _ClientServerCompatibilityTest_ starts a server node with _Runner.java_, 
> _PlatformProcessUtils#startProcess()_ and stops with 
> _PlatformProcessUtils#stopProcess()_. On Windows, additional 
> {code:java}
>  serverProc.KillProcessTree();
> {code}
> is applied.
> We should wait until _java.lang.Process_ completely stops. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to