[Ndn-lib] ndn-js proxy crash FYI
wentaoshang at gmail.com
Fri Mar 15 17:53:56 PDT 2013
Thanks for discovering this bug. After some analysis I believe the crash is
caused by the situation when the client first asks for a data and then
closes websocket connection before the server returns the answer. The proxy
would then write to a broken tcp connection and throw an exception. I
pushed a new version of wsproxy-tcp.js to the github, which should solve
this issue. Can you help test the new code on our app box?
On Fri, Mar 15, 2013 at 1:18 PM, Alexander Horn <alexnano at ucla.edu> wrote:
> it's great to see ndn-js getting used in multiple projects.
> ws-proxy is pretty stable on the app boxes... yet last night, after a few
> weeks of uptime the ws-proxy on UCLA app box crashed.
> ccndstatus indicates route to hub was still up; box appeared normal - ccnd
> & route up, online... just no ws-proxy.
> The only thing different about this app box, is it's
> directly communicating w/ Wentao's latest ndn-js client for BMS/repo data.
> I have full packet capture via ws-proxy logging (15MB) if wanted;
> meanwhile here's stderr:
> else throw new Error('not opened');
> Error: not opened
> at WebSocket.send
> at Socket.<anonymous>
> at Socket.EventEmitter.emit (events.js:96:17)
> Ndn-lib mailing list
> Ndn-lib at lists.cs.ucla.edu
PhD student @ Internet Research Lab, Computer Science Department,
University of California, Los Angeles
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ndn-lib