[
https://issues.apache.org/jira/browse/IGNITE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487839#comment-15487839
]
Dmitry Karachentsev commented on IGNITE-3054:
---------------------------------------------
* Fixed bugs that lead to ExecutionTimeout of the tests.
* Now SSL works OK, but on Linux machine often receive exceptions on handshake,
like: *"javax.net.ssl.SSLException: Received fatal alert: <UNKNOWN ALERT:
206>"* with random codes, or real reasons, but it looks like data mess on
connection process. Exactly the same issue like
[here|http://stackoverflow.com/questions/34671460/getting-various-sslexceptions-when-running-loadtest-on-an-ssl-enabled-url-call].
Trying to understand the nature of that error.
> Rework client connection handling from thread-per-client to NIO model.
> ----------------------------------------------------------------------
>
> Key: IGNITE-3054
> URL: https://issues.apache.org/jira/browse/IGNITE-3054
> Project: Ignite
> Issue Type: Task
> Components: general
> Affects Versions: 1.5.0.final
> Reporter: Vladimir Ozerov
> Assignee: Dmitry Karachentsev
> Fix For: 1.8
>
>
> Currently both servers and clients has the same operational model -
> thread-per-connection. While being more or less fine for servers, this could
> be a problem for clients when their total number is too high (e.g. 1000 or
> even more).
> We should rework client handling model and employ standard NIO technique: one
> or several acceptor threads + thread pool to server requests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
