Details
-
Type: Monitor
-
Status: Closed
-
Priority: Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
Labels:
-
HD-Chapter:Data
-
HD-Enabler:Orion
Description
Created question in FIWARE Q/A platform on 14-06-2016 at 09:06
Please, ANSWER this question AT 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": [
],
"attributes": [],
"reference": "http://172.21.0.23:5050/notify",
"duration": "P1M",
"notifyConditions": [
]
}
EOF
One temporal solution seems to be to establish a very large duration period. Is that neccessary?
2016-06-14 12:05|CREATED monitor | # answers= 1, accepted answer= False