You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@openmeetings.apache.org by "Maxim Solodovnik (Jira)" <ji...@apache.org> on 2020/05/02 16:35:00 UTC

[jira] [Resolved] (OPENMEETINGS-2331) KMS connectivity isn't auto-recovering

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

Maxim Solodovnik resolved OPENMEETINGS-2331.
--------------------------------------------
    Fix Version/s: 5.0.0-M5
       Resolution: Fixed

The code should be more bullet-proof now
please reopen with additional details if still an issue

> 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)