Actions
Bug #2174
open
Multiple register prefix gives NFD error "request timed out (code: 10060)"
Status:
New
Priority:
Normal
Assignee:
-
Category:
RIB
Target version:
-
Start date:
11/13/2014
Due date:
% Done:
0%
Estimated time:
Description
We came across this issue when trying to register multiple prefixes in a group chat application.
To reproduce: Start NFD with the installed defaults in a separate window so you can see errors. Modify the ndn-cxx examples/producer.cpp run method to register 300 different prefixes. https://github.com/named-data/ndn-cxx/blob/b6783065ae24f4035a95d7ab6effd81b720a6f23/examples/producer.cpp#L80 . Replace:
m_face.setInterestFilter("/example/testApp",
bind(&Producer::onInterest, this, _1, _2),
RegisterPrefixSuccessCallback(),
bind(&Producer::onRegisterFailed, this, _2));
with:
for (int x = 1; x <= 300; ++x) {
std::ostringstream prefix;
prefix << "/example/testApp" << x;
m_face.setInterestFilter(prefix.str(),
bind(&Producer::onInterest, this, _1, _2),
RegisterPrefixSuccessCallback(),
bind(&Producer::onRegisterFailed, this, _2));
}
In ndn-cxx, compile and run the producer:
./waf configure --with-examples
./waf
build/examples/producer
Expected result: All prefixes are registered.
Actual result: After a few seconds, NFD prints the following error several times:
[RibManager] NFD returned an error: request timed out (code: 10060)
It also prints the following error a few times:
[RibManager] NFD returned an error: Face not found (code: 410)
Finally, it prints:
Face Status Dataset request timed out
Many of the prefixes are not registered, presumably related to the above messages.
Updated by 
Updated by 
Updated by 
Updated by
Actions