[Ndn-lib] ndn-js proxy crash FYI
wentaoshang at gmail.com
Sat Mar 16 18:15:04 PDT 2013
Actually I'm not very familiar with the configuration of ccnr and ccnd
routing. I just used the 'ndnucla-staging' URL that Alex gave to me as the
default proxy hub. On borges I only publish the data into repo without
configuring any ccnd routes. Somehow the current configuration works. Not
sure if other proxy hub could also work...
On Sat, Mar 16, 2013 at 3:23 PM, Burke, Jeff <jburke at remap.ucla.edu> wrote:
> I think the round-robin that Alex describes below is supposed to be the
> default behavior of the library.
> Is the data you're publishing routable across the testbed? It should be
> From: Alexander Horn <alexnano at ucla.edu>
> Date: Sat, 16 Mar 2013 14:38:09 -0700
> To: Wentao Shang <wentaoshang at gmail.com>
> Cc: "ndn-lib at lists.cs.ucla.edu" <ndn-lib at lists.cs.ucla.edu>
> Subject: Re: [Ndn-lib] ndn-js proxy crash FYI
> great !
> i've updated it, and I have proxy at ndnucla-staging hub on an
> auto-recover loop that stores crash logs.
> let's see how it behaves today; i'll push both to all appboxes tomorrow.
> at some point it would be wise to make your web page round-robin w/ the
> hubs... though not sure if Jeff wants to do that before monday's demo?
> depends how confident we are in testbed connectivity :)
> A.ws.ndn.ucla.edu <http://a.ws.ndn.ucla.edu/> [PARC]
> B.ws.ndn.ucla.edu <http://b.ws.ndn.ucla.edu/> [UCLA-APPS-STAGING]
> C.ws.ndn.ucla.edu <http://c.ws.ndn.ucla.edu/> [ARIZONA]
> D.ws.ndn.ucla.edu <http://d.ws.ndn.ucla.edu/> [CAIDA]
> E.ws.ndn.ucla.edu <http://e.ws.ndn.ucla.edu/> [ILLINOIS]
> On Fri, Mar 15, 2013 at 5:53 PM, Wentao Shang <wentaoshang at gmail.com>wrote:
>> Hi Alex,
>> 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
> _______________________________________________ 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