Same here, I get kicked off more often then not. When I first get into the main venue I usually can stay on about 50% of the time at least for a couple of hours. For every level I drop down into the venues I only have a 50% chance again to stay in that venue (50% of 50% is 25% and so on and so forth). One I get kicked off that's the end. It just kicks and kicks and etc... The only way to get my chances again is to close the venue client completely(making sure all python processes die because sometimes they don't) and restarting the venue client. This gets me back to my chances again. It usually takes me around 10 times to get into the venue I need to get into.
And now that you mention it, it does seem to get faster when it invites me again and then kicks me over and over again. I am on 2.2 on a Multi-Node with Windows running my Venue Client and audio and Fedora running my Video. Just thought that I would let you know it's not just you :-) Thanks Adam Taylor Computing Center University of Louisiana at Monroe -----Original Message----- From: owner-ag-t...@mcs.anl.gov [mailto:owner-ag-t...@mcs.anl.gov] On Behalf Of Markus Buchhorn Sent: Monday, July 26, 2004 9:47 PM To: ag-t...@mcs.anl.gov Subject: [AG-TECH] venue client problems Hi all@ag-dev On a 2.2 node (venue client on Windows) I can enter and move around the APAG venue server (2.1.2 from memory?) fine, but have all sorts of problems entering and moving around the ANL venue server. Typical behaviour is 1. I get kicked off, 2. I get invited to reconnect 3. I get kicked off before I have fully reconnected 4. Repeat 2-3 at ever faster rate. Occassionally I get in and can stay in, on the main Lobby venue. If I try and enter the Institutional Lobby though it takes a looooong time, and then eventually enters the main Lobby again - not letting me drop down to lower venues at all. Then after all a while I get kicked off (see above :-) ). Also: There doesn't seem to be any way to say to the venue client to cancel an attempt to enter a venue. So if there's any problems getting into a venue, it effectively hangs the venue client. Timeouts might help, but there's too many places where some delays might occur. It'd be nice if the venue client could provide fairly detailed state-information as to where it is up to when changing venues ('killing/ed rat, killing/ed vic, entering/ed venue, starting/ed vic, starting/ed rat, things should be normal now, ...' :-) ). Is there any plan for a minor update to 2.2 to fix these things (if you know what is causing them), or is 2.3 close? scglobal is looming. Cheers, Markus Markus Buchhorn, ANU Internet Futures Group, |Ph: +61 2 61258810 markus.buchh...@anu.edu.au, mail: Bldg #108 CS&IT |Fx: +61 2 61259805 The Australian National University, Canberra 0200 |Mob: 0417 281429
