[AG-TECH] AG3.1: Blocked VenueClient when connecting to Server
Michael Braitmaier
braitmaier at hlrs.de
Wed Aug 22 07:00:40 CDT 2007
In fact I kept both client and server running through lunch time and
after more than an hour the client was still in a state
where it didn't respond to any keypress or mouse click.
So far I don't think it is directly related to what you describe.
Michael
Christoph Willing schrieb:
>
> On 22/08/2007, at 8:01 PM, Michael Braitmaier wrote:
>
>> I am recently trying to connect with a venueclient to a venueserver
>> on the same machine(WinXP, no MC). However both client and server are
>> blocking once they reached a
>> specfific part in the process. From the log-files, I can't make up
>> anything unusual except the fact that I disabled starting of the
>> Beacon service (see #Bug 1701)
>>
>> I attached the last parts of my logs from the server and the client
>> as far as they created output befor entering blocking state.
>> After that I can only kill the venueclient process through the task
>> manager and then normally exit the server with ALT-C.
>>
>> I encountered the same behaviour on a second machine (WinXP, MC) both
>> times using the latest CVS code of AG3.1 beta-1.
>> There is no further log-output being created from that point on until
>> I kill the venueclient.
>>
>> I hope someone can give me a hint.
>
>
> Michael,
>
> How long have you waited after the inactivity began? I have noticed
> what at first appears to be blocking like you describe but I always
> (so far) see some activity within about 30-40 seconds. In fact, this
> upper limit has made me wonder whether its connected with the
> heartbeat timer. - when looking at the VenueClient debugging output,
> the inactivity stops about the time that the next heartbeat occurs.
>
> The delay I'm seeing is not constant; although there is sometimes this
> long delay, at other times there is no delay at all.
>
> I've also noticed that this problem affects not just venue entering
> but also event distribution for shared applications e.g. reception of
> "next page" events in Shared Presentation.
>
>
> chris
>
>
>> VenueServer:
>> 08/22/07 11:16:39 4052 VenueServer venue.py:488 INFO User None
>> authorized for action NegotiateCapabilities
>> 08/22/07 11:16:39 4052 VenueServer venue.py:839 DEBUG negotiate
>> capabilities
>> 08/22/07 11:16:39 4052 VenueServer venue.py:848 DEBUG Capability
>> to be processed: producer, Beacon, 1, ANY, 0, 1, None, None
>> 08/22/07 11:16:39 4052 VenueServer venue.py:848 DEBUG Capability
>> to be processed: consumer, Beacon, 1, ANY, 0, 1, None, None
>> 08/22/07 11:16:39 4052 VenueServer venue.py:893 DEBUG Stream
>> doesn't exist create new one!
>> 08/22/07 11:16:39 4052 VenueServer venue.py:898 DEBUG Stream
>> type: Beacon!
>> 08/22/07 11:16:39 4052 VenueServer venue.py:909 DEBUG Caps:
>> producer, Beacon, 1, ANY, 0, 1, None, None
>> 08/22/07 11:16:39 4052 VenueServer venue.py:909 DEBUG Caps:
>> consumer, Beacon, 1, ANY, 0, 1, None, None
>> 08/22/07 11:16:39 4052 VenueServer venue.py:915 DEBUG Stream
>> prefers multicast!
>> 08/22/07 11:16:39 4052 VenueServer venue.py:918 DEBUG Stream
>> address: 224.2.180.121 : 59880
>> 08/22/07 11:16:39 4052 VenueServer venue.py:928 DEBUG added user
>> as producer of non-existent stream
>> 08/22/07 11:16:39 4052 VenueServer venue.py:2405 DEBUG * * *
>> Added stream producer 8d3a080a0e9427af990bb4fb9d26cfe6
>> 08/22/07 11:16:39 4052 VenueServer venue.py:933 DEBUG sending
>> AddStream event; stream=StreamDescription: {'description': None,
>> 'encryptionKey': None, 'uri': None, 'encryptionFlag': 0,
>> 'capability': [producer, Beacon, 1, ANY, 0, 1, None, None, consumer,
>> Beacon, 1, ANY, 0, 1, None, None], 'static': 0, 'location': multicast
>> 224.2.180.121 59880 127, 'id': '8d3a080a0e9427af99190577042d1dbb',
>> 'networkLocations': [multicast 224.2.180.121 59880 127], 'name':
>> 'Venue Server Lobby'}
>>
>> VenueClient:
>> 08/22/07 11:16:37 3916 VenueClient venueclient.py:1210 DEBUG
>> EnterVenue; url=https://141.58.8.10:8000/Venues/default type=<type
>> 'str'>
>> 08/22/07 11:16:37 3916 NodeService agnodeservice.py:664 INFO
>> NodeService.GetCapabilities
>> 08/22/07 11:16:37 3916 NodeService agnodeservice.py:258 INFO
>> NodeService.GetServices
>> 08/22/07 11:16:37 2736 ServiceManager agservicemanager.py:220
>> INFO AGServiceManager.GetServices
>> 08/22/07 11:16:37 3916 VenueClient venueclient.py:1222 DEBUG
>> Capability on VenueEnter: producer, Beacon, 1, ANY, 0, 1, None, None
>> 08/22/07 11:16:37 3916 VenueClient venueclient.py:1222 DEBUG
>> Capability on VenueEnter: consumer, Beacon, 1, ANY, 0, 1, None, None
>> 08/22/07 11:16:37 3916 VenueClient venueclient.py:1247 DEBUG
>> calling __EnterVenue
>> 08/22/07 11:16:37 3916 VenueClient venueclient.py:999 DEBUG
>> EnterVenue: Invoke Venue.Enter
>> 08/22/07 11:16:39 3916 VenueClient venueclient.py:1001 DEBUG
>> after Venue.Enter
>> 08/22/07 11:16:39 3916 VenueClient venueclient.py:1003 DEBUG
>> EnterVenue: Invoke Venue.getstate
>> 08/22/07 11:16:39 3916 VenueClient venueclient.py:1005 DEBUG
>> EnterVenue: done Venue.getstate
>> 08/22/07 11:16:39 3916 VenueClient venueclient.py:1028 DEBUG
>> Setting isInVenue flag.
>> 08/22/07 11:16:39 3916 VenueClient venueclient.py:1249 DEBUG
>> after __EnterVenue
>> 08/22/07 11:16:39 3024 VenueClient venueclient.py:589 DEBUG
>> Calling Heartbeat, time now: 1187774199
>> 08/22/07 11:16:39 3916 VenueClient venueclientui.py:3185 DEBUG
>> EnterVenue: Enter venue with url:
>> https://141.58.8.10:8000/Venues/default
>> 08/22/07 11:16:40 3916 VenueClient venueclientui.py:3252 DEBUG
>> Load Venue data store data
>>
>> --
>> ------------------
>> Dipl.-Inf. Michael Braitmaier
>> HLRS - Visualization / Video Conferencing
>> University of Stuttgart
>> Germany
>> Website: http://www.hlrs.de/people/braitmaier/
>>
>
> Christoph Willing +61 7 3365 8350
> QCIF Access Grid Manager
> University of Queensland
>
>
>
>
--
------------------
Dipl.-Inf. Michael Braitmaier
HLRS - Visualization / Video Conferencing
University of Stuttgart
Germany
Phone: ++49 711 685 65996
Fax : ++49 711 682 357
Website: http://www.hlrs.de/people/braitmaier/
More information about the ag-tech
mailing list