[Backlogmanager] [FIWARE-JIRA] (HELP-6775) FIWARE.Question.Tech.Fiware - Orion Context Broker subscription expiration.

[Fernando Lopez (JIRA)]

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

Fernando Lopez reassigned HELP-6775:
------------------------------------

    Assignee: Fermín Galán

> FIWARE.Question.Tech.Fiware - Orion Context Broker subscription expiration.
> ---------------------------------------------------------------------------
>
>                 Key: HELP-6775
>                 URL: https://jira.fiware.org/browse/HELP-6775
>             Project: Help-Desk
>          Issue Type: Monitor
>          Components: FIWARE-TECH-HELP
>            Reporter: Backlog Manager
>            Assignee: Fermín Galán
>              Labels: fiware, fiware-orion
>
> Created question in FIWARE Q/A platform on 14-06-2016 at 09:06
> {color: red}Please, ANSWER this question AT{color} http://stackoverflow.com/questions/37805708/fiware-orion-context-broker-subscription-expiration
> +Question:+
> Fiware - Orion Context Broker subscription expiration
> +Description:+
> I'm working with Orion context Broker version 1.0.0. I have an active subscription constantly receiving notifications that should be redirected to a cygnus. 
> My concern is that last thursday this subscription did expire. Theorically, while a subscription keeps sending notifications to it's subscribers, the expiration date is updated. Then, anyone knows why that active subscription did expire?
> That's how I do the subscription registrations: 
> (curl 172.21.0.33:1026/v1/subscribeContext -s -S --header 'Fiware-Service: xxxx' --header 'Fiware-ServicePath: /xxxx/xxxx' --header 'Content-Type: application/json' --header 'Accept: application/json' -d  @- | python -mjson.tool) <<EOF
> {
>     "entities": [
>         {
>             "type": "tmp_reading",
>             "isPattern": "true",
>             "id": ".*"
>         }
>     ],
>     "attributes": [],
>     "reference": "http://172.21.0.23:5050/notify",
>     "duration": "P1M",
>     "notifyConditions": [
>         {
>             "type": "ONCHANGE",
>             "condValues": []
>         }
>     ]
> }
> EOF  
> One temporal solution seems to be to establish a very large duration period. Is that neccessary?



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