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

FIWARE.Question.Tech.'fiware-servicepath' header value does not match the number of notified context responses.

    Details

      Description

      Created question in FIWARE Q/A platform on 01-10-2018 at 14:10
      Please, ANSWER this question AT https://stackoverflow.com/questions/52591735/fiware-servicepath-header-value-does-not-match-the-number-of-notified-context

      Question:
      'fiware-servicepath' header value does not match the number of notified context responses

      Description:
      Working on setting cygnus as sink to CKAN, and i get this error, what part of Cygnus setup is responsible for this( subscription, configuration ...)

      cygnus_1 | time=2018-10-01T12:40:04.517Z | lvl=DEBUG | corr=1ea858dc-c577-
      11e8-b0fd-0242ac140003 | trans=5c553916-f5e6-4bbc-b98a-bcaba61a306c |
      srv=waste4think | subsrv=/room/test | comp=cygnus-ngsi | op=getEvents |
      msg=com.telefonica.iot.cygnus.handlers.NGSIRestHandler[320] :
      [NGSIRestHandler] Parsed NotifyContextRequest:

      {" subscriptionId":"5bb2153fd1bde90f8813b236","originator":"null","contextResponse s":[]}

      I assume error is conected to this contextResponses because it is empty, but i found no additional info what is causing this where i should look. And error is not helping.

      This is more general question that issue since i cannot call this issue because i have no idea if it is me who is causing this or cygnus have indeed some problems.

      Thanks.

        Activity

        fla Fernando Lopez made changes -
        Fix Version/s 2021 [ 12600 ]
        fla Fernando Lopez made changes -
        HD-Enabler CKAN [ 10870 ]
        Description
        Created question in FIWARE Q/A platform on 01-10-2018 at 14:10
        {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/52591735/fiware-servicepath-header-value-does-not-match-the-number-of-notified-context


        +Question:+
        'fiware-servicepath' header value does not match the number of notified context responses

        +Description:+
        Working on setting cygnus as sink to CKAN, and i get this error, what part of Cygnus setup is responsible for this( subscription, configuration ...)

        cygnus_1 | time=2018-10-01T12:40:04.517Z | lvl=DEBUG | corr=1ea858dc-c577-
        11e8-b0fd-0242ac140003 | trans=5c553916-f5e6-4bbc-b98a-bcaba61a306c |
        srv=waste4think | subsrv=/room/test | comp=cygnus-ngsi | op=getEvents |
        msg=com.telefonica.iot.cygnus.handlers.NGSIRestHandler[320] :
        [NGSIRestHandler] Parsed NotifyContextRequest:{"
        subscriptionId":"5bb2153fd1bde90f8813b236","originator":"null","contextResponse
        s":[]}


        I assume error is conected to this contextResponses because it is empty, but i found no additional info what is causing this where i should look. And error is not helping.

        This is more general question that issue since i cannot call this issue because i have no idea if it is me who is causing this or cygnus have indeed some problems.

        Thanks.
        Created question in FIWARE Q/A platform on 01-10-2018 at 14:10
        {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/52591735/fiware-servicepath-header-value-does-not-match-the-number-of-notified-context


        +Question:+
        'fiware-servicepath' header value does not match the number of notified context responses

        +Description:+
        Working on setting cygnus as sink to CKAN, and i get this error, what part of Cygnus setup is responsible for this( subscription, configuration ...)

        cygnus_1 | time=2018-10-01T12:40:04.517Z | lvl=DEBUG | corr=1ea858dc-c577-
        11e8-b0fd-0242ac140003 | trans=5c553916-f5e6-4bbc-b98a-bcaba61a306c |
        srv=waste4think | subsrv=/room/test | comp=cygnus-ngsi | op=getEvents |
        msg=com.telefonica.iot.cygnus.handlers.NGSIRestHandler[320] :
        [NGSIRestHandler] Parsed NotifyContextRequest:{"
        subscriptionId":"5bb2153fd1bde90f8813b236","originator":"null","contextResponse
        s":[]}


        I assume error is conected to this contextResponses because it is empty, but i found no additional info what is causing this where i should look. And error is not helping.

        This is more general question that issue since i cannot call this issue because i have no idea if it is me who is causing this or cygnus have indeed some problems.

        Thanks.
        backlogmanager Backlog Manager made changes -
        Summary [fiware-stackoverflow] 'fiware-servicepath' header value does not match the number of notified context responses FIWARE.Question.Tech.'fiware-servicepath' header value does not match the number of notified context responses.
        joaquin.salvachua Joaquín Salvachúa made changes -
        Assignee Joaquín Salvachúa [ joaquin.salvachua ] Andres Muñoz [ andres.munoza ]
        backlogmanager Backlog Manager made changes -
        Resolution Done [ 10000 ]
        Status Answered [ 10104 ] Closed [ 6 ]
        backlogmanager Backlog Manager made changes -
        Status In Progress [ 3 ] Answered [ 10104 ]
        backlogmanager Backlog Manager made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        veronika Veronika Vlnkova made changes -
        Assignee Joaquín Salvachúa [ joaquin.salvachua ]
        backlogmanager Backlog Manager made changes -
        Field Original Value New Value
        Component/s FIWARE-TECH-HELP [ 10278 ]
        backlogmanager Backlog Manager created issue -

          People

          • Assignee:
            andres.munoza Andres Muñoz
            Reporter:
            backlogmanager Backlog Manager
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: