The only thing that I know that the recordings kept disconnecting, so I checked the log to see this error in multiple occurrences.

On 10/17/20 3:45 PM, Ali Alhaidary wrote:

To tell you the truth, I do not know. I was checking the log and saw this error, and have no clue of why, when or what happened...

On 10/17/20 2:48 PM, Maxim Solodovnik wrote:
What are the steps?

On Sat, 17 Oct 2020 at 00:03, Ali Alhaidary <ali.alhaid...@the5stars.org <mailto:ali.alhaid...@the5stars.org>> wrote:

    could not record continuously with multiple occurrences of the
    following
    error:

    DEBUG 10-16 16:51:24.012 o.a.o.c.r.KStream:291 [nio-5443-exec-1] -
    PARTICIPANT cf00f402-dd38-49dc-8c62-75a6f26feabf: Releasing listeners
      WARN 10-16 16:51:24.019 o.a.o.c.r.KStream:371 [ventExec-e3-t17] -
    PARTICIPANT cf00f402-dd38-49dc-8c62-75a6f26feabf: Could not
    disconnect
    recorder
    org.kurento.jsonrpc.JsonRpcErrorException: Object
    
'a05e48f8-685f-4579-a0e2-3e5bcb7f980d_kurento.MediaPipeline/47a5c8a0-5043-4038-9de4-b33067b2753f_kurento.WebRtcEndpoint'

    not found. Code: 40101. Data: {"type":"MEDIA_OBJECT_NOT_FOUND"}
         at
    
org.kurento.jsonrpc.internal.JsonRpcRequestSenderHelper$1.onSuccess(JsonRpcRequestSenderHelper.java:128)
         at
    
org.kurento.jsonrpc.internal.JsonRpcRequestSenderHelper$1.onSuccess(JsonRpcRequestSenderHelper.java:113)
         at
    
org.kurento.jsonrpc.client.AbstractJsonRpcClientWebSocket$14.onSuccess(AbstractJsonRpcClientWebSocket.java:452)
         at
    
org.kurento.jsonrpc.client.AbstractJsonRpcClientWebSocket$14.onSuccess(AbstractJsonRpcClientWebSocket.java:433)
         at
    
com.google.common.util.concurrent.Futures$CallbackListener.run(Futures.java:1089)
         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)

    Any idea?



--
Best regards,
Maxim

Reply via email to