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:IoT
-
HD-Enabler:IoT Broker
Description
Created question in FIWARE Q/A platform on 25-05-2016 at 20:05
Please, ANSWER this question AT http://stackoverflow.com/questions/37445486/iot-broker-seems-to-disagree-with-iot-discovery
Question:
IoT Broker seems to disagree with IoT Discovery
Description:
I have the next configuration:
IoTBroker(v.5.2.3) <-----> IotDicovery(v.4.3)
when I issue a
GET **/ngsi10/contextEntities/EntityName**
message to the IoTBroker it automatically generates a
**/ngsi9/discoverContext/Availability**
query to the IoTDiscovery. The IoTDiscovery then answers positively with a
200 OK HTTP message
with the information about the EntityName required.
The problem is that when the IoTBroker makes the final response, it responds with a 404 NOT FOUND HTTP Message.
This is the post being automatically generated by the IoTBroker to the the IoTDiscovery:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<discoverContextAvailabilityRequest>
<entityIdList>
<entityId isPattern="false">
<id>Room</id>
</entityId>
</entityIdList>
<attributeList/>
<restriction>
<attributeExpression>
</attributeExpression>
<scope>
<operationScope>
<scopeType>
IncludeAssociations
</scopeType>
<scopeValue xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xsi:type="xs:string">
SOURCES
</scopeValue>
</operationScope>
</scope>
</restriction>
</discoverContextAvailabilityRequest>
and this is the response from the IoTDiscovery to the IoTBroker, where apparently everything is OK:
<?xml version="1.0" encoding="UTF-8"?><discoverContextAvailabilityResponse>
<contextRegistrationResponseList>
<contextRegistrationResponse>
<contextRegistration>
<entityIdList>
<entityId type="Room" isPattern="false">
<id>ConferenceRoom</id>
</entityId>
</entityIdList>
<contextRegistrationAttributeList>
<contextRegistrationAttribute>
<name>temperature</name>
<type>degree</type>
<isDomain>false</isDomain>
<metadata>
<contextMetadata>
<name>unit</name>
<type>string</type>
<value/>
</contextMetadata>
</metadata>
</contextRegistrationAttribute>
</contextRegistrationAttributeList>
<providingApplication>http://192.168.100.1:70/tempApplication
...</providingApplication>
</contextRegistration>
</contextRegistrationResponse>
</contextRegistrationResponseList>
<errorCode>
<code>200</code>
<reasonPhrase>OK</reasonPhrase>
<details xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">Result</details>
</errorCode>
</discoverContextAvailabilityResponse>
Activity
Falls du im lab bist, kannst Du den Statis suf 'started' bzw 'analyzing' setzen.
Best regards / MfG
Stefan Gessler
----------------------------------
Edited and sent from my smartphone (so pls excuse typos and abbr.)
> Am 26.05.2016 um 08:31 schrieb Backlog Manager (JIRA) <jira-help-desk@fi-ware.org>:
>
>
> [ https://jira.fiware.org/browse/HELP-6669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Backlog Manager reassigned HELP-6669:
> -------------------------------------
>
> Assignee: Stefan Gessler
>
>> [fiware-stackoverflow] IoT Broker seems to disagree with IoT Discovery
>> ----------------------------------------------------------------------
>>
>> Key: HELP-6669
>> URL: https://jira.fiware.org/browse/HELP-6669
>> Project: Help-Desk
>> Issue Type: Monitor
>> Components: FIWARE-TECH-HELP
>> Reporter: Backlog Manager
>> Assignee: Stefan Gessler
>> Labels: fiware, fiware-orion, xml
>>
>> Created question in FIWARE Q/A platform on 25-05-2016 at 20:05
>> Please, ANSWER this question AT http://stackoverflow.com/questions/37445486/iot-broker-seems-to-disagree-with-iot-discovery
>> Question:
>> IoT Broker seems to disagree with IoT Discovery
>> Description:
>> I have the next configuration:
>> IoTBroker(v.5.2.3) <-----> IotDicovery(v.4.3)
>> when I issue a
>> GET **/ngsi10/contextEntities/EntityName**
>> message to the IoTBroker it automatically generates a
>> **/ngsi9/discoverContext/Availability**
>> query to the IoTDiscovery. The IoTDiscovery then answers positively with a
>> 200 OK HTTP message
>> with the information about the EntityName required.
>> The problem is that when the IoTBroker makes the final response, it responds with a 404 NOT FOUND HTTP Message.
>> This is the post being automatically generated by the IoTBroker to the the IoTDiscovery:
>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
>> <discoverContextAvailabilityRequest>
>> <entityIdList>
>> <entityId isPattern="false">
>> <id>Room</id>
>> </entityId>
>> </entityIdList>
>> <attributeList/>
>> <restriction>
>> <attributeExpression>
>> </attributeExpression>
>> <scope>
>> <operationScope>
>> <scopeType>
>> IncludeAssociations
>> </scopeType>
>> <scopeValue xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> xmlns:xs="http://www.w3.org/2001/XMLSchema"
>> xsi:type="xs:string">
>> SOURCES
>> </scopeValue>
>> </operationScope>
>> </scope>
>> </restriction>
>> </discoverContextAvailabilityRequest>
>> and this is the response from the IoTDiscovery to the IoTBroker, where apparently everything is OK:
>> <?xml version="1.0" encoding="UTF-8"?><discoverContextAvailabilityResponse>
>> <contextRegistrationResponseList>
>> <contextRegistrationResponse>
>> <contextRegistration>
>> <entityIdList>
>> <entityId type="Room" isPattern="false">
>> <id>ConferenceRoom</id>
>> </entityId>
>> </entityIdList>
>> <contextRegistrationAttributeList>
>> <contextRegistrationAttribute>
>> <name>temperature</name>
>> <type>degree</type>
>> <isDomain>false</isDomain>
>> <metadata>
>> <contextMetadata>
>> <name>unit</name>
>> <type>string</type>
>> <value/>
>> </contextMetadata>
>> </metadata>
>> </contextRegistrationAttribute>
>> </contextRegistrationAttributeList>
>> <providingApplication>http://192.168.100.1:70/tempApplication
>> ...</providingApplication>
>> </contextRegistration>
>> </contextRegistrationResponse>
>> </contextRegistrationResponseList>
>> <errorCode>
>> <code>200</code>
>> <reasonPhrase>OK</reasonPhrase>
>> <details xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">Result</details>
>> </errorCode>
>> </discoverContextAvailabilityResponse>
>
>
>
> –
> This message was sent by Atlassian JIRA
> (v6.4.1#64016)
2016-05-25 21:05|CREATED monitor | # answers= 0, accepted answer= False