[Backlogmanager] [FIWARE-JIRA] (HELP-14735) FIWARE.Question.Tech.' fiware-servicepath' header value does not match the number of notified context responses.

[Fernando Lopez (JIRA)]

     [ https://jira.fiware.org/browse/HELP-14735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fernando Lopez updated HELP-14735:
----------------------------------
    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.


  was:

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.


     HD-Enabler: CKAN

> FIWARE.Question.Tech.'fiware-servicepath' header value does not match the number of notified context responses.
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: HELP-14735
>                 URL: https://jira.fiware.org/browse/HELP-14735
>             Project: Help-Desk
>          Issue Type: Monitor
>          Components: FIWARE-TECH-HELP
>            Reporter: Backlog Manager
>            Assignee: Andres Muñoz
>              Labels: fiware, fiware-cygnus
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.4.1#64016)