liuxiangdong created OPENMEETINGS-2075:
------------------------------------------

             Summary: Can't record
                 Key: OPENMEETINGS-2075
                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2075
             Project: Openmeetings
          Issue Type: Bug
          Components: Converters
    Affects Versions: 5.0.0-M1
         Environment: server system: ubuntu18.04
client system: Win10
web browser: Chrome

            Reporter: liuxiangdong
            Assignee: Maxim Solodovnik
         Attachments: image-2019-05-30-16-25-56-011.png, 
image-2019-05-30-16-28-22-874.png

!image-2019-05-30-16-25-56-011.png!

!image-2019-05-30-16-28-22-874.png!

 

After click "Start recording" button, output the following log.

DEBUG 05-30 07:42:32.118 o.a.o.c.r.KurentoHandler:221 [nio-5443-exec-2] - 
Searching for room 7
DEBUG 05-30 07:42:32.118 o.a.o.c.r.KurentoHandler:235 [nio-5443-exec-2] - Room 
7 found!
DEBUG 05-30 07:42:32.119 o.a.o.c.r.KRoom:195 [nio-5443-exec-2] - ##REC:: 
recording in room 7 is stopping 12 ::
DEBUG 05-30 07:42:32.207 o.a.o.c.c.RecordingConverter:52 [taskExecutor-5] - 
recording 12
ERROR 05-30 07:42:32.219 o.a.o.c.c.RecordingConverter:111 [taskExecutor-5] - 
[startConversion]
org.apache.openmeetings.core.converter.ConversionException: screenMetaData is 
Null recordingId 12
 at 
org.apache.openmeetings.core.converter.RecordingConverter.startConversion(RecordingConverter.java:59)
 at 
org.apache.openmeetings.core.remote.StreamProcessor.lambda$startConvertion$9(StreamProcessor.java:435)
 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)
DEBUG 05-30 07:42:32.228 o.a.o.c.u.WebSocketHelper:123 [nio-5443-exec-2] - 
Sending WebSocket message to room: recordingToggled
DEBUG 05-30 07:42:32.228 o.a.o.c.r.KRoom:220 [nio-5443-exec-2] - ##REC:: 
recording in room 7 is stopped ::



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to