cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9348) CloudStack Server degrades when a lot of connections on port 8250
Date Thu, 06 Apr 2017 07:45:41 GMT


ASF GitHub Bot commented on CLOUDSTACK-9348:

Github user rhtyd commented on the issue:
    @marcaurele the test makes use of threads to run various clients and server instances
and is known to consume ports for the same, for these reasons it might fail in some test/build
environments. If you look at the git history on this test file and on the pom.xml, you'll
find that this test had been disabled in the past (before PR 1493) due to these issues. The
test is known to fail intermittently in CI environments such as Jenkins and Travis, which
is why I added to the ignored list of test with one of the PRs.
    On my workstation, I've been consistently able to run and pass it, it is likely an environment
issue in your laptop if this is failing inconsistently.

> CloudStack Server degrades when a lot of connections on port 8250
> -----------------------------------------------------------------
>                 Key: CLOUDSTACK-9348
>                 URL:
>             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:
> 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

View raw message