There was a network outage at the university, preventing the registry bootstrap (peers.txt) file from being retrieved.
For 3.0.2 clients, this meant no bridge list whatsoever, as the bridge list is built every time the client starts up. For 3.1 clients, this only meant slow startup. The 3.1 client caches the bridge list, so uses the cached list when the registry can't be contacted. (Improvement!) We'll need to add code to impose a reasonable timeout on the registry access, to fix the slow startup problem for the future. Longer term plans include replacing the central registry with peer-to-peer infrastructure, to remove the single point of failure, but that's some way off. Tom On 12/18/07 11:14 AM, Todd Zimmerman wrote: > My venueclient is hanging on start up, and running in debug it appears to be > hanging while trying to > connect to http://www.accessgrid.org/registry/peers.txt I've confirmed I > cannot connect via browser > to www.accessgrid.org either. > > It eventually does timeout after (a fairly excruciating) 3 minutes... anyway > to shorten this timeout > and/or to workaround the single point of failure? > > > Cheers, > > Todd > > >
