G'day Jean Basically what is happening is the AG3 Venue Client is trying to contact each of the unicast bridges before loading (In case you need to use unicast, rather than Multicast). What unfortuantly has been occuring is that 1 or more Unicast bridges are located behind firewalls, which cause our Venue Client to not be able to contact them and hence the long loading times.
After a few minutes, this will time out and will load the Venue Client. This is a known problem and will hopefully be resolved in the next release (3.1) Hope this helps. Cheers, Jason. -----Original Message----- From: Jean Utke [mailto:u...@mcs.anl.gov] Sent: Wednesday, 15 November 2006 01:39 AM To: ag-t...@mcs.anl.gov Subject: [AG-TECH] Registryclient Hi, While trying to set up my AG3 client I noticed a debug message: 11/14/2006 09:30:27 AM 1076399968 RegistryClient RegistryClient.py:73 INFO Using deprecated ping for older bridge interface to vv3.accessgrid.or.kr:22000 and was wondering if there is a problem with my installation and why it would go to a host in Korea if I am sitting at Argonne (that is, if the message text is reflecting what actually happens) Just curious. Thanks, Jean -- Jean Utke Argonne National Lab./MCS u...@mcs.anl.gov phone: 630 252 4552 cell: 630 363 5753
