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

_______________________________________________
Fiware-tech-help mailing list
Fiware-tech-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-tech-help

Dear Lorenzo,

Thanks for contacting us. I assume that you can continue your work now.

Regards,

Miguel

El 07/07/2015 a las 11:18, Lorenzo Trisolini escribió:
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.
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.

Lorenzo Trisolini

2015-07-06 17:17 GMT+02:00 Lorenzo Trisolini <lore.trisolini@gmail.com<lore.trisolini@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</reference>
......
</subscribeContextAvailabilityRequest>

When the IoT discovery tries to send a NotifyContextAvailabilityRequest() to 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

there is a bug to be resolved.  Iot-discovery and IoT Bróker must assess on what Ge implementation this is and the Ge owner of the culprit must fix the bug

???

this one is already closed since a long time, any bug in the 'reminder' system?

Stefan

-------------------------------------------------------
Stefan Gessler
Project Manager and Data Protection Officer
NEC Europe Ltd.
Kurfuersten Anlage 36
D-69115 Heidelberg
GERMANY

phone +49 6221 4342 114
fax +49 6221 4342 155
email: stefan.gessler@neclab.eu

-