[Nfd-dev] ERROR:error while connecting to the forwarder

[Junxiao Shi]

Hi John

Thank you.
We look forward to your patch submitted to NDN Gerrit http://gerrit.named-data.net 

Yours, Junxiao


From: JohnQi
Sent: Sunday, August 30, 2015 23:59
To: Junxiao Shi
Subject: Re:RE: [Nfd-dev] ERROR:error while connecting to the forwarder


Thanks for your immediate reply！

We are trying to do our effort to solve this problem and provide a patch.




At 2015-08-27 21:31:34, "Junxiao Shi" <shijunxiao at email.arizona.edu> wrote:

Hi John
 
This is either due to Bug 2742, or caused by too many prefix registration commands filling up the output buffer of the UNIX socket before Face::processEvents is invoked.
The solution would be: during traffic generator server initialization, call Face::processEvents after every prefix registration command.
Currently ndn-traffic-generator does not have a maintainer. Can you contribute a patch to this problem? The patch can be submitted to Gerrit.
 
Yours, Junxiao
 

From: JohnQi
Sent: Thursday, August 27, 2015 02:10
To: nfd-dev at lists.cs.ucla.edu
Subject: Re: [Nfd-dev] ERROR:error while connecting to the forwarder
 
 
Hi! Every one,
 
 We are woking on an experiment on NFD. To evaluate the performance of the NFD, we try to use the traffic-generator provided with the NFD together. We wrote two configuration files according to "ndn-traffic-server.conf.sample" and "ndn-traffic-client.conf.sample". The only difference between our configuration files and the orginal configuration files lie on the number of the content in the files. Our files include 10 thousands of content.  Then I started the nfd at the client and the server. Moreover, registered the name prefix by binding the sever ip.
There is an error ocured then with a msg that "error while connecting to the forwarder" (we have correctly run and compile NFD and ndn-traffic-generator). Our configure files "ndn-traffic-server.conf.sample, ndn-traffic-server.conf.sample.full-data, ndn-traffic-client.conf.sample" are attached in this mail.
To identify this error, we constructed another configure files and found that there is no error at all if the number of the content in the configuration files is less then 1936. This two configuration files are attatched also. 
I think this is a bug of the NFD in consideration of the simplicity of the  traffic-generator.  Does anybody know about this? Please do us a favor to check this problem. 
Looking forward to your reply. Thanks a lot.
 
Yours sincerely.
John qi.

夏日畅销榜大牌美妆只要1元


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20150831/8c8b9e86/attachment.html>