[
https://issues.apache.org/jira/browse/OPENMEETINGS-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17098123#comment-17098123
]
Konstantin Kuzov edited comment on OPENMEETINGS-2331 at 5/2/20, 11:01 PM:
--------------------------------------------------------------------------
On build #3175 it's even somewhat worse: [https://pastebin.com/xsCyvWUx]. Same
test case of restarting KMS during already running OM with couple of users in
the same chat-room.
After KMS restart stacktraces [1] and [2] from pastedbin starts spamming for a
while. At user activity [3] stacktrace appears. If users try to exit through
exit button they get invalid page error and "ghost" user appears. If they try
refresh by F5 then same stuck user but without error page. After some time
reconnection attempts gave up so there are no more [1]. Also there are no more
"Media Server is not accessible" messages nor on clients nor in log after bunch
of initial ones.
Full log with two consecutive tests
[here|https://nosferatu.g0x.ru/openmeetings.log]. Both failed.
was (Author: nosferatu):
On build #3175 it's even somewhat worse: [https://pastebin.com/xsCyvWUx]. Same
test case of restarting KMS during already running OM with couple of users in
the same chat-room.
After KMS restart stacktraces [1] and [2] from pastedbin starts spamming for a
while. At user activity [3] stacktrace appears. If users try to exit through
exit button they get invalid page error and "ghost" user appears. If they try
refresh by F5 then same stuck user but without error page. After some time
reconnection attempts gave up so there are no more [1].
Full log with two consecutive tests
[here|https://nosferatu.g0x.ru/openmeetings.log]. Both failed.
> KMS connectivity isn't auto-recovering
> --------------------------------------
>
> Key: OPENMEETINGS-2331
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2331
> Project: Openmeetings
> Issue Type: Bug
> Components: Kurento
> Affects Versions: 5.0.0-M4
> Reporter: Konstantin Kuzov
> Assignee: Maxim Solodovnik
> Priority: Major
> Fix For: 5.0.0-M5
>
>
> If OM was started after Kurento Media Server then all is well and dandy. But
> if KMS was started after OM or was restarted for some reason later (for
> example due to update or crash) then OM will never recover from that and
> currently require full OM restart.
> There should be some auto-recovery mechanism in place which will continuously
> try to reinitiate connection (with configurable intervals) to KMS until a new
> connection is established.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
