[
https://issues.apache.org/jira/browse/IGNITE-17119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17551557#comment-17551557
]
Roman Puchkovskiy commented on IGNITE-17119:
--------------------------------------------
This was caused by two problems:
1. Some JDK versions (including 1.8.0_261) contain a bug
https://bugs.openjdk.java.net/browse/JDK-8241239 due to which close() on a
socket is blocked when a write() is blocked on its output stream. This causes
the test to always fail on such JDKs. The test models a situation which may be
faced by our customers, so there is no point in working this around just in our
test.
2. If the original 'handshake' takes long time (I saw it around 1 second), then
the test may block on a write attempt for a long time (handshake time
multiplied by 10), in my case 10 seconds, which makes the test fail.
We can't do anything with item 1, but we did alleviate item 2: write wait time
is bounded.
> DiscoveryClientSocketTest.sslSocketTest fails regularly on TC and locally
> -------------------------------------------------------------------------
>
> Key: IGNITE-17119
> URL: https://issues.apache.org/jira/browse/IGNITE-17119
> Project: Ignite
> Issue Type: Bug
> Components: networking
> Reporter: Roman Puchkovskiy
> Assignee: Roman Puchkovskiy
> Priority: Major
> Fix For: 2.14
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=1051723478826841368&tab=testDetails
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
