You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "Konstantin Kuzov (Jira)" <ji...@apache.org> on 2020/05/01 15:46:00 UTC
[jira] [Comment Edited] (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=17097457#comment-17097457 ] 

Konstantin Kuzov edited comment on OPENMEETINGS-2331 at 5/1/20, 3:45 PM:
-------------------------------------------------------------------------

Build #3169, docker with kms restartarted during operation:
{noformat}
 INFO 05-01 18:33:27.068 o.k.j.c.JsonRpcClientNettyWebSocket:275 [ntLoopGroup-2-1] - [KurentoClient] channel closed
 INFO 05-01 18:33:27.082 o.a.o.c.r.KurentoHandler:378 [EventExec-e2-t6] - Kurento disconnected
 WARN 05-01 18:33:27.082 o.a.o.c.r.KurentoHandler:380 [EventExec-e2-t6] - Disconnected, will re-try in 10000 ms
 WARN 05-01 18:33:27.082 o.a.o.c.r.KurentoHandler:115 [EventExec-e2-t6] - Media Server is not accessible
 WARN 05-01 18:33:27.091 o.k.j.c.AbstractJsonRpcClientWebSocket:484 [EventExec-e2-t6] - [KurentoClient] Exception sending close message. org.kurento.jsonrpc.JsonRpcClientClosedException:Trying to send a message in a client closed explicitly. When a client is closed, it can't be reused. It is necessary to create another one
 WARN 05-01 18:33:27.095 o.a.o.c.r.KurentoHandler:115 [Thread-37] - Media Server is not accessible
DEBUG 05-01 18:33:27.096 o.a.o.d.d.r.PollDao:104 [Thread-37] - :: hasPoll :: 40
 WARN 05-01 18:33:27.097 o.k.j.c.AbstractJsonRpcClientWebSocket:657 [nnectExec-e3-t0] - [KurentoClient] Exception trying to reconnect to server ws://127.0.0.1:8888/kurento. Retrying in 2000 ms
org.kurento.jsonrpc.JsonRpcClientClosedException: Trying to send a message in a client closed explicitly. When a client is closed, it can't be reused. It is necessary to create another one
 at org.kurento.jsonrpc.client.AbstractJsonRpcClientWebSocket.internalConnectIfNecessary(AbstractJsonRpcClientWebSocket.java:702)
 at org.kurento.jsonrpc.client.AbstractJsonRpcClientWebSocket.connectIfNecessary(AbstractJsonRpcClientWebSocket.java:847)
 at org.kurento.jsonrpc.client.AbstractJsonRpcClientWebSocket$16.run(AbstractJsonRpcClientWebSocket.java:635)
 at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
 at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
 at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
 at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
 at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
 at java.base/java.lang.Thread.run(Thread.java:834)
 INFO 05-01 18:33:27.100 o.a.o.c.r.KurentoHandler:378 [EventExec-e2-t7] - Kurento disconnected
 WARN 05-01 18:33:27.107 o.k.j.c.AbstractJsonRpcClientWebSocket:484 [EventExec-e2-t6] - [KurentoClient] Exception sending close message. org.kurento.jsonrpc.JsonRpcClientClosedException:Trying to send a message in a client closed explicitly. When a client is closed, it can't be reused. It is necessary to create another one
 WARN 05-01 18:33:27.111 o.k.j.c.JsonRpcClientNettyWebSocket:308 [EventExec-e2-t6] - [KurentoClient] Trying to close a JsonRpcClientNettyWebSocket with channel == null
 WARN 05-01 18:33:27.111 o.k.j.c.JsonRpcClientNettyWebSocket:291 [EventExec-e2-t6] - [KurentoClient] Trying to close a JsonRpcClientNettyWebSocket with group == null
 INFO 05-01 18:33:27.113 o.a.o.c.r.KurentoHandler:378 [EventExec-e4-t0] - Kurento disconnected
DEBUG 05-01 18:33:27.114 o.a.o.c.r.KStream:293 [EventExec-e2-t6] - PARTICIPANT 80bb7472-0a34-4563-a0e1-eddb16146da9: Releasing listeners
DEBUG 05-01 18:33:27.117 o.a.o.d.d.r.PollDao:98 [Thread-37] - :: getArchived :: 40
 WARN 05-01 18:33:27.127 o.a.o.c.r.KurentoHandler:115 [Thread-37] - Media Server is not accessible
 WARN 05-01 18:33:27.128 o.a.o.c.r.KurentoHandler:115 [Thread-37] - Media Server is not accessible
 WARN 05-01 18:33:34.409 o.a.o.c.r.KurentoHandler:115 [nio-5443-exec-2] - Media Server is not accessible
 WARN 05-01 18:33:34.416 o.a.o.c.r.KurentoHandler:115 [nio-5443-exec-2] - Media Server is not accessible
 WARN 05-01 18:33:34.422 o.a.o.c.r.KurentoHandler:115 [nio-5443-exec-2] - Media Server is not accessible
 WARN 05-01 18:33:34.429 o.a.o.c.r.KurentoHandler:115 [nio-5443-exec-2] - Media Server is not accessible
 WARN 05-01 18:33:34.435 o.a.o.c.r.KurentoHandler:115 [nio-5443-exec-2] - Media Server is not accessible
 WARN 05-01 18:33:34.458 o.a.o.c.r.KurentoHandler:115 [nio-5443-exec-6] - Media Server is not accessible
 WARN 05-01 18:33:34.464 o.a.o.c.r.KurentoHandler:115 [nio-5443-exec-6] - Media Server is not accessible
 WARN 05-01 18:33:34.506 o.a.o.c.r.KurentoHandler:115 [nio-5443-exec-4] - Media Server is not accessible
 WARN 05-01 18:33:34.512 o.a.o.c.r.KurentoHandler:115 [nio-5443-exec-4] - Media Server is not accessible
DEBUG 05-01 18:33:41.024 o.a.o.w.c.OmWebSocketPanel:88 [nio-5443-exec-5] - Sending WebSocket PING
DEBUG 05-01 18:34:11.058 o.a.o.w.c.OmWebSocketPanel:88 [nio-5443-exec-3] - Sending WebSocket PING
{noformat}
After that there are just spam about Media Server is not accessible on client activity and nothing else


was (Author: nosferatu):
Build #3169, docker with kms restartarted during operation:
{noformat}
 INFO 05-01 18:33:27.068 o.k.j.c.JsonRpcClientNettyWebSocket:275 [ntLoopGroup-2-1] - [KurentoClient] channel closed
 INFO 05-01 18:33:27.082 o.a.o.c.r.KurentoHandler:378 [EventExec-e2-t6] - Kurento disconnected
 WARN 05-01 18:33:27.082 o.a.o.c.r.KurentoHandler:380 [EventExec-e2-t6] - Disconnected, will re-try in 10000 ms
 WARN 05-01 18:33:27.082 o.a.o.c.r.KurentoHandler:115 [EventExec-e2-t6] - Media Server is not accessible
 WARN 05-01 18:33:27.091 o.k.j.c.AbstractJsonRpcClientWebSocket:484 [EventExec-e2-t6] - [KurentoClient] Exception sending close message. org.kurento.jsonrpc.JsonRpcClientClosedException:Trying to send a message in a client closed explicitly. When a client is closed, it can't be reused. It is necessary to create another one
 WARN 05-01 18:33:27.095 o.a.o.c.r.KurentoHandler:115 [Thread-37] - Media Server is not accessible
DEBUG 05-01 18:33:27.096 o.a.o.d.d.r.PollDao:104 [Thread-37] - :: hasPoll :: 40
 WARN 05-01 18:33:27.097 o.k.j.c.AbstractJsonRpcClientWebSocket:657 [nnectExec-e3-t0] - [KurentoClient] Exception trying to reconnect to server ws://127.0.0.1:8888/kurento. Retrying in 2000 ms
org.kurento.jsonrpc.JsonRpcClientClosedException: Trying to send a message in a client closed explicitly. When a client is closed, it can't be reused. It is necessary to create another one
 at org.kurento.jsonrpc.client.AbstractJsonRpcClientWebSocket.internalConnectIfNecessary(AbstractJsonRpcClientWebSocket.java:702)
 at org.kurento.jsonrpc.client.AbstractJsonRpcClientWebSocket.connectIfNecessary(AbstractJsonRpcClientWebSocket.java:847)
 at org.kurento.jsonrpc.client.AbstractJsonRpcClientWebSocket$16.run(AbstractJsonRpcClientWebSocket.java:635)
 at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
 at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
 at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
 at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
 at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
 at java.base/java.lang.Thread.run(Thread.java:834)
 INFO 05-01 18:33:27.100 o.a.o.c.r.KurentoHandler:378 [EventExec-e2-t7] - Kurento disconnected
 WARN 05-01 18:33:27.107 o.k.j.c.AbstractJsonRpcClientWebSocket:484 [EventExec-e2-t6] - [KurentoClient] Exception sending close message. org.kurento.jsonrpc.JsonRpcClientClosedException:Trying to send a message in a client closed explicitly. When a client is closed, it can't be reused. It is necessary to create another one
 WARN 05-01 18:33:27.111 o.k.j.c.JsonRpcClientNettyWebSocket:308 [EventExec-e2-t6] - [KurentoClient] Trying to close a JsonRpcClientNettyWebSocket with channel == null
 WARN 05-01 18:33:27.111 o.k.j.c.JsonRpcClientNettyWebSocket:291 [EventExec-e2-t6] - [KurentoClient] Trying to close a JsonRpcClientNettyWebSocket with group == null
 INFO 05-01 18:33:27.113 o.a.o.c.r.KurentoHandler:378 [EventExec-e4-t0] - Kurento disconnected
DEBUG 05-01 18:33:27.114 o.a.o.c.r.KStream:293 [EventExec-e2-t6] - PARTICIPANT 80bb7472-0a34-4563-a0e1-eddb16146da9: Releasing listeners
DEBUG 05-01 18:33:27.117 o.a.o.d.d.r.PollDao:98 [Thread-37] - :: getArchived :: 40
 WARN 05-01 18:33:27.127 o.a.o.c.r.KurentoHandler:115 [Thread-37] - Media Server is not accessible
 WARN 05-01 18:33:27.128 o.a.o.c.r.KurentoHandler:115 [Thread-37] - Media Server is not accessible
 WARN 05-01 18:33:34.409 o.a.o.c.r.KurentoHandler:115 [nio-5443-exec-2] - Media Server is not accessible
 WARN 05-01 18:33:34.416 o.a.o.c.r.KurentoHandler:115 [nio-5443-exec-2] - Media Server is not accessible
 WARN 05-01 18:33:34.422 o.a.o.c.r.KurentoHandler:115 [nio-5443-exec-2] - Media Server is not accessible
 WARN 05-01 18:33:34.429 o.a.o.c.r.KurentoHandler:115 [nio-5443-exec-2] - Media Server is not accessible
 WARN 05-01 18:33:34.435 o.a.o.c.r.KurentoHandler:115 [nio-5443-exec-2] - Media Server is not accessible
 WARN 05-01 18:33:34.458 o.a.o.c.r.KurentoHandler:115 [nio-5443-exec-6] - Media Server is not accessible
 WARN 05-01 18:33:34.464 o.a.o.c.r.KurentoHandler:115 [nio-5443-exec-6] - Media Server is not accessible
 WARN 05-01 18:33:34.506 o.a.o.c.r.KurentoHandler:115 [nio-5443-exec-4] - Media Server is not accessible
 WARN 05-01 18:33:34.512 o.a.o.c.r.KurentoHandler:115 [nio-5443-exec-4] - Media Server is not accessible{noformat}
After that there are just spam about Media Server is not accessible on client activity and nothing else

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