[Fiware-tech-help] IoT Broker 4.3.3

[Lorenzo Trisolini]

Hi,
maybe I've resolved the problem. The iot-discovery send the
notifyContextAvailabilityRequest() using as url in the POST,
*http://127.0.1.1:8090/ngsi9
<http://127.0.1.1:8090/ngsi9>.*
But I've verified (modifing the code of the iot discovery vers.4.2) that
IoTBroker receives notifyContextAvailabilityRequest() only if the
iotDiscovery (vers. 4.2) uses this url
*http://127.0.1.1:8090/ngsi9/notifyContextAvailability
<http://127.0.1.1:8090/ngsi9/notifyContextAvailability>.*

Lorenzo Trisolini

2015-07-06 17:17 GMT+02:00 Lorenzo Trisolini <lore.trisolini at gmail.com>:

> I'm Lorenzo Trisolini, student of university of pisa. I deployed an
> instance of IoT Broker 4.3.3 and an instance of IoT Discovery 4.2. I've a
> problem with the ngsi10 operation, subscribe context. I do:
>
> POST http://localhost:8090/ngsi10/subscribeContext
> <?xml version="1.0" encoding="UTF-8"?>
> <subscribeContextRequest>
> .......
> ......
> </subscribeContextRequest>
>
> the IoT discovery receives this request from the IoTBroker:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <subscribeContextAvailabilityRequest>
> ........
>   <reference>*http://127.0.1.1:8090/ngsi9 <http://127.0.1.1:8090/ngsi9>*
> </reference>
> ......
> </subscribeContextAvailabilityRequest>
>
> When the IoT discovery tries to send a NotifyContextAvailabilityRequest()
> to *http://127.0.1.1:8090/ngsi9 <http://127.0.1.1:8090/ngsi9>*, the
> IoTBroker response is:
>
> .....
>
> \t\t\t\t<h1><strong><font size="20">404 Page Not Found!</font></strong></h1>\t\r\n
>
> ......
>
>
> Best Regards,
>
> Lorenzo Trisolini
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-tech-help/attachments/20150707/33e61e6a/attachment.html>