Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-7271

FIWARE.Request.Tech.Data.Stream-oriented.Kurento, Firefox jsonrpc timeout kills nodejs app

    Details

    • Type: extRequest
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Fix Version/s: 2021
    • Component/s: FIWARE-TECH-HELP
    • Labels:
      None
    • HD-Chapter:
      Data
    • HD-Enabler:
      Kurento

      Description

      Dear FIWARE coach,
      we forward you a support request received from a CreatiFI applicant we are
      not able to solve.
      Please let us know if you need direct contact with the submitter.
      Thanks.

      ************************

      I'm working on getting Firefox to work (Chrome works fine). Sometimes I see
      this exception only with Firefox. It occurs after the session is closed and
      the recordings are being stopped. The recording fails (zero byte file). The
      node app must be restarted after this. I dont see any errors in the kurento
      server log - is there something I could look for?

      thanks
      Paul

      Trace: { [Error: Request has timed out]
      room-0 request:
      '{"jsonrpc":"2.0","method":"invoke","params":

      {"object":"604800d8-b1e9-4a96-80fb-2130e03fbc11_kurento.MediaPipeline/68d52395-f33c-490a-bd47-4688c94f7c1c_kurento.RecorderEndpoint","operation":"stop","sessionId":"8ee31d88-a2c1-4b49-b3c2-70454089d867"}

      ,"id":1981}',
      room-0 retry: [Function: retry] }
      room-0 at RecorderEndpoint.noop
      (/home/paul_davies/uxprobe/kurento-room-app/node_modules/kurento-client/node_modules/kurento-client-core/lib/abstracts/UriEndpoint.js:35:22)
      room-0 at callback2
      (/home/paul_davies/uxprobe/kurento-room-app/node_modules/kurento-client/node_modules/promisecallback/index.js:27:25)
      room-0 at tryCatch
      (/home/paul_davies/uxprobe/kurento-room-app/node_modules/kurento-client/node_modules/es6-promise/dist/es6-promise.js:410:12)
      room-0 at invokeCallback
      (/home/paul_davies/uxprobe/kurento-room-app/node_modules/kurento-client/node_modules/es6-promise/dist/es6-promise.js:425:13)
      room-0 at publish
      (/home/paul_davies/uxprobe/kurento-room-app/node_modules/kurento-client/node_modules/es6-promise/dist/es6-promise.js:393:7)
      room-0 at publishRejection
      (/home/paul_davies/uxprobe/kurento-room-app/node_modules/kurento-client/node_modules/es6-promise/dist/es6-promise.js:335:3)
      room-0 at flush
      (/home/paul_davies/uxprobe/kurento-room-app/node_modules/kurento-client/node_modules/es6-promise/dist/es6-promise.js:121:5)
      room-0 at nextTickCallbackWith0Args (node.js:420:9)
      room-0 at process._tickDomainCallback (node.js:390:13)

      ************************

      Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
      Please, send your messages using the new domain (Fiware-creatifi-coaching@lists.fiware.org) instead of the old one.
      _______________________________________________
      Fiware-creatifi-coaching mailing list
      Fiware-creatifi-coaching@lists.fiware.org
      https://lists.fiware.org/listinfo/fiware-creatifi-coaching
      [Created via e-mail received from: Andrea Maestrini <amaestrini@create-net.org>]

        Issue Links

          Activity

          Hide
          llopez NaevaTeC Development Team added a comment -

          What node version are you using? There is an open issue with node 6.X promises, so we recommend you to use 4.X LTS instead.

          Since some errors are asynchronous, and thus raised as an event, you can subscribe also to error events from the pipeline and the recorder. Otherwise, you'd need to check the KMS logs for errors.

          Show
          llopez NaevaTeC Development Team added a comment - What node version are you using? There is an open issue with node 6.X promises, so we recommend you to use 4.X LTS instead. Since some errors are asynchronous, and thus raised as an event, you can subscribe also to error events from the pipeline and the recorder. Otherwise, you'd need to check the KMS logs for errors.
          Hide
          llopez NaevaTeC Development Team added a comment -

          Since we have not received any update, we are going to close this issue.

          Show
          llopez NaevaTeC Development Team added a comment - Since we have not received any update, we are going to close this issue.

            People

            • Assignee:
              llopez NaevaTeC Development Team
              Reporter:
              fw.ext.user FW External User
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: