[
https://issues.apache.org/jira/browse/CLOUDSTACK-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13464437#comment-13464437
]
Mice Xia commented on CLOUDSTACK-215:
-------------------------------------
[root cause]
1）when assign console proxy to a VNC request, should check if the candidate
CPVM has reached the max session
2）SQL GET_PROXY_ACTIVE_LOAD in ConsoleProxyDaoImpl is incorrect, no column
'proxy_id' in table console_proxy
> CPVM load balance didn't work, VNC console sessions go to one CPVM and ignore
> other CPVMs
> -----------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-215
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-215
> Project: CloudStack
> Issue Type: Bug
> Components: VNC Proxy
> Affects Versions: pre-4.0.0
> Reporter: Mice Xia
> Assignee: Mice Xia
> Fix For: pre-4.0.0
>
>
> [reproduce steps]
> 1) setting global configs:
> consoleproxy.session.max = 5
> consoleproxy.capacity.standby = 3
> 2) open 8 VM VNC console
> [expected result]
> a new CPVM will be started
> old CPVM takes 5 sessions, the new one takes 3 sessions
> [observed result]
> a new CPVM will be started
> old CPVM takes 8 sessions, the new one take 0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
