[
https://issues.apache.org/jira/browse/CLOUDSTACK-9348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272518#comment-15272518
]
ASF GitHub Bot commented on CLOUDSTACK-9348:
--------------------------------------------
Github user swill commented on the pull request:
https://github.com/apache/cloudstack/pull/1493#issuecomment-217188135
@rhtyd I am still having problems with the tests in this PR, but now it is
in master.
This is causing builds to fail...
```
testConnection(com.cloud.utils.testcase.NioTest) Time elapsed: 300.073 sec
<<< ERROR!
org.junit.runners.model.TestTimedOutException: test timed out after 300000
milliseconds
at java.lang.Thread.sleep(Native Method)
at com.cloud.utils.testcase.NioTest.testConnection(NioTest.java:146)
```
> CloudStack Server degrades when a lot of connections on port 8250
> -----------------------------------------------------------------
>
> Key: CLOUDSTACK-9348
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9348
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Rohit Yadav
> Assignee: Rohit Yadav
> Fix For: 4.9.0
>
>
> An intermittent issue was found with a large CloudStack deployment, where
> servers could not keep agents connected on port 8250.
> All connections are handled by accept() in NioConnection:
> https://github.com/apache/cloudstack/blob/master/utils/src/main/java/com/cloud/utils/nio/NioConnection.java#L125
> A new connection is handled by accept() which does blocking SSL handshake. A
> good fix would be to make this non-blocking and handle expensive tasks in
> separate threads/pool. This way the main IO loop won't be blocked and can
> continue to serve other agents/clients.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
