[ 
https://issues.apache.org/jira/browse/OPENMEETINGS-2355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konstantin Kuzov updated OPENMEETINGS-2355:
-------------------------------------------
    Description: 
After [OPENMEETINGS-2315] and [OPENMEETINGS-2316] some stream connections 
states not terminating fully and there are growing list of stale streams in 
admin->connections (look at stale-processors.png).
It happens randomly, most likely due to unreliable network, slow devices or 
browser quirks.
I found the only one reliable way to reproduce this using android's chrome 
which also unearth reconnection problem:
 - enter the room with one another participant
 - not closing tab with om, just switch to another tab with random page. 
Another participant will see frozen image.
 - wait around 10 seconds and switch back, on your end you will see fully 
working webcam, but on participant's end the image will still be frozen.
 - after another 5 seconds there will be a message on both ends about trying to 
reconnect which will result in fast refresh already seamingly working camera on 
android chrome, but on another participant there will be only empty window with 
avatar. And it will stay that way forever. At that point android user can exit 
the room and his stream will stuck.


  was:
After [OPENMEETINGS-2315] and [OPENMEETINGS-2316] some stream connections 
states not terminating fully and there are growing list of stale streams in 
admin->connections (look at stale-processors.png).
It happens randomly, most likely due to unreliable network, slow devices or 
browser quirks.
I found the only one reliable way to reproduce this using android's chrome 
which also unearth reconnection problem:
 - enter the room with one another participant
 - not closing tab with om, just switch to another tab with random page. 
Another participant will see frozen image.
 - wait around 10 seconds and switch back, on your end you will see fully 
working webcam, but on participant's end the image will still be frozen.
 - after around another 5 seconds there will be a message on both ends about 
trying to reconnect which will result in fast refresh already seamingly working 
camera on android chrome, but on another participant there will be only empty 
window with avatar. And it will stay that way forever. At that point android 
user can exit the room and his stream will stuck.



> Growing list of stream connection in admin->connections
> -------------------------------------------------------
>
>                 Key: OPENMEETINGS-2355
>                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2355
>             Project: Openmeetings
>          Issue Type: Bug
>          Components: Room
>    Affects Versions: 5.0.0-M5
>            Reporter: Konstantin Kuzov
>            Assignee: Maxim Solodovnik
>            Priority: Major
>         Attachments: stale-processors.png
>
>
> After [OPENMEETINGS-2315] and [OPENMEETINGS-2316] some stream connections 
> states not terminating fully and there are growing list of stale streams in 
> admin->connections (look at stale-processors.png).
> It happens randomly, most likely due to unreliable network, slow devices or 
> browser quirks.
> I found the only one reliable way to reproduce this using android's chrome 
> which also unearth reconnection problem:
>  - enter the room with one another participant
>  - not closing tab with om, just switch to another tab with random page. 
> Another participant will see frozen image.
>  - wait around 10 seconds and switch back, on your end you will see fully 
> working webcam, but on participant's end the image will still be frozen.
>  - after another 5 seconds there will be a message on both ends about trying 
> to reconnect which will result in fast refresh already seamingly working 
> camera on android chrome, but on another participant there will be only empty 
> window with avatar. And it will stay that way forever. At that point android 
> user can exit the room and his stream will stuck.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to