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

Posted to commits@openmeetings.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/05/01 09:41:00 UTC

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

    [ https://issues.apache.org/jira/browse/OPENMEETINGS-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17097272#comment-17097272 ] 

ASF subversion and git services commented on OPENMEETINGS-2331:
---------------------------------------------------------------

Commit 85e9a4d212c3c323050227ed53341358b1541956 in openmeetings's branch refs/heads/master from Maxim Solodovnik
[ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=85e9a4d ]

[OPENMEETINGS-2331] some additional logging


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