Description of problem:
Usability problem with serial-console. Unable to kick-off stuck or active serial-console connection.

In case I'm connected from one terminal towards VM over serial console and I want to get connected to the same VM from another terminal, I can't kick-off the first active or stuck session. 

Version-Release number of selected component (if applicable):
Engine:
rhevm-3.6.0.3-0.1.el6.noarch
ovirt-vmconsole-proxy-1.0.0-1.el6ev.noarch                                         
ovirt-engine-extension-aaa-jdbc-1.0.1-1.el6ev.noarch                 
ovirt-host-deploy-1.4.0-1.el6ev.noarch                                                  
ovirt-host-deploy-java-1.4.0-1.el6ev.noarch                                            
ovirt-vmconsole-1.0.0-1.el6ev.noarch

Host:
ovirt-vmconsole-host-1.0.1-0.0.master.20151105234454.git3e5d52e.el7.noarch
ovirt-release36-snapshot-001-2.noarch
ovirt-vmconsole-1.0.1-0.0.master.20151105234454.git3e5d52e.el7.noarch
ovirt-release36-001-2.noarch


How reproducible:
100%

Steps to Reproduce:
1.Connect to VM over serial-console from first terminal.
2.Try connecting from second terminal to the same VM over serial-console.
3.You can't kick-off the first active/stuck serial-console session.

Actual results:
You can't kick-off the first active/stuck serial-console session.

Expected results:
Customer should have the capability to end active/stuck serial-console session, for example if that is the same customer and he/she wants to establish serial-console connection from another terminal or he/she knows that session is stuck and would like to drop it, without waiting for the session time-out to expire.

Additional info: