Quantcast
Channel: VMware Communities : All Content - VMware View
Viewing all articles
Browse latest Browse all 9103

Very slow to get the available desktops in View 5.2

$
0
0

Hi all,

 

I met a strange issues when I tried to log in View 5.2 connection server. The issue is: some physical machines are very slow to get available desktops. After you input the connection server ip address in the Windows view client and go to next, it cost very long time (almost 50s) to display the available desktops. But for some other physical desktops, the time is quite short (~4s).

 

From the <vdm-logs>/<logon user>/debug.log in the desktop in trouble, I can see the following snippets. You can see there are 12s between "brokerConnect started" and "brokerConnect successful", and there are 17s between "brokerLogon started" and "brokerLogon successful". And the client tried twice to brokerLogon.

2013-11-13T14:39:20.390+08:00 DEBUG (0CB4-0CD8) <MessageFrameWorkDispatch> [wswc_http] Broker request brokerConnect started

2013-11-13T14:39:32.433+08:00 DEBUG (0CB4-0CD8) <MessageFrameWorkDispatch> [wswc_http] Broker request brokerConnect successful

2013-11-13T14:39:40.358+08:00 DEBUG (0CB4-0CD8) <MessageFrameWorkDispatch> [wswc_http] Broker request brokerLogon started

2013-11-13T14:39:57.971+08:00 DEBUG (0CB4-0CD8) <MessageFrameWorkDispatch> [wswc_http] Broker request brokerLogon successful

2013-11-13T14:40:10.295+08:00 DEBUG (0CB4-0CD8) <MessageFrameWorkDispatch> [wswc_http] Broker request brokerLogon started

2013-11-13T14:40:11.090+08:00 DEBUG (0CB4-0CD8) <MessageFrameWorkDispatch> [wswc_http] Broker request brokerLogon successful

2013-11-13T14:40:11.090+08:00 DEBUG (0CB4-0CD8) <MessageFrameWorkDispatch> [wswc_http] Broker request brokerGetDesktops started

2013-11-13T14:40:11.199+08:00 DEBUG (0CB4-0CD8) <MessageFrameWorkDispatch> [wswc_http] Broker request brokerGetDesktops successful

From the <vdm-logs>/<logon user>/debug.log in the normal desktop, I can see the time between broerConnect started and successful are quite short, so does between brokerLogon started and successful. And the client tried only once to brokerLogon.

2013-11-13T09:38:10.174+08:00 DEBUG (0A4C-0D98) <MessageFrameWorkDispatch> [wswc_http] Broker request brokerConnect started

2013-11-13T09:38:10.424+08:00 DEBUG (0A4C-0D98) <MessageFrameWorkDispatch> [wswc_http] Broker request brokerConnect successful

2013-11-13T09:38:13.749+08:00 DEBUG (0A4C-0D98) <MessageFrameWorkDispatch> [wswc_http] Broker request brokerLogon started

2013-11-13T09:38:14.467+08:00 DEBUG (0A4C-0D98) <MessageFrameWorkDispatch> [wswc_http] Broker request brokerLogon successful

2013-11-13T09:38:14.467+08:00 DEBUG (0A4C-0D98) <MessageFrameWorkDispatch> [wswc_http] Broker request brokerGetDesktops started

2013-11-13T09:38:14.763+08:00 DEBUG (0A4C-0D98) <MessageFrameWorkDispatch> [wswc_http] Broker request brokerGetDesktops successful

 

  1. I use ip address (not URL) to connect to connection server.
  2. For the physical desktop in trouble, I have tried Windows XP SP3 32 bit, Windows 7 32 bit and Windows 7 64 bit.
    1. For Windows XP SP3 32 bit and Windows 7 32 bit, I have tried View windows client 5.1, 5.3 and 5.4
  3. For the connection server, I have tried version 5.1 and 5.2

 

Any thought about this issue? Thanks!


Viewing all articles
Browse latest Browse all 9103

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>