login vsi company logo login vsi company logo 250x40
header-02.jpg

Forum Announcement

The Login VSI forum has been disabled and now only serves as an archive. If you would like to submit a new support ticket, please send an email to support@loginvsi.com.

Medium Workload stuck 0%

  • Raffelstetter
  • Raffelstetter's Avatar Topic Author
22 Jun 2013 19:37 #1190

Hi,
we are testing LoginVSI Express with 10 User sessions on a single XenApp server. 9/10 sessions stuck at Segment Prepare 0%




Second problem is that the sessions won't get logged off.

Any idea?
Thanks!

Attachments:

Please Log in to join the conversation.

More
26 Jun 2013 11:45 #1205

Hi Raffel,

Looks like IE is not running in protected mode, which is required for specific IE versions, and that’s why IE is hanging (it’s trying to focus and maximize the BBC page).

A few troubleshoot steps;

Did you ran our AD-prep phase for the creation of test users, or, do you use your own test users?
Are the VSI GPO's (both System/User) applied for your test users?
Which IE version is installed on your XenApp host?
Is IE running the websites (BBC etc.) in Protected Mode (Both Internet and Intranet Zones)?

Hoping to hear from you soon.

Thanks,

Omar.

Please Log in to join the conversation.

  • Raffelstetter
  • Raffelstetter's Avatar Topic Author
26 Jun 2013 12:38 #1207

Hi,
thanks for your support!
The workload works now, the path to the store in some files was wrong.

Logoff still won't work, all sessions logged on and all workloads starting but the sessions are not logged of when the test ends.

Kind Regards

Please Log in to join the conversation.

More
26 Jun 2013 14:23 #1210

Hi Raffel,

Your welcome. You didn't answer my questions though(...) The VSI Team appreciates all the needs and help when we troubleshoot.

For the logoff mechanism, are you sure you configured VSI to initiate the logoff command for the test? Attached is a screenshot.

Let me know.

Thanks,

Omar.

Attachments:

Please Log in to join the conversation.

  • Raffelstetter
  • Raffelstetter's Avatar Topic Author
26 Jun 2013 14:25 #1211

Hi,
sorry ;)
Yes, the setting is activated and is set to 120sec.

Kind Regards,

Please Log in to join the conversation.

More
26 Jun 2013 15:00 #1213

Hi Raffel,

I assume that the users are still active and running the test. Be patient :)

A few checks; check the VSIShare\_VSI_Logfiles\TESTFOLDER\
and check when the x-amount of seconds is reached whether there is a file called Logoff.txt ? Means that the initiate sequence is processed/successfully.

We launch 10 sessions to your Target, we initiate the logoff sequence when we launch the last session, by default the logoff sequence from the user is 'Logoff at "Timer"' which means when a Timer is reached/finished the user checks if there is a Logoff.txt in the TESTFOLDER. Now as you may notice (depends) User 1,2,3 may be already at a Timer when the Logoff.txt is already placed, but for the User 4,5 ... 10 not. Each segment has 3 Timers, each segment takes up to ~12min. (The whole loop is then; 4 segments x 12min. = 48min., 4segments x 3 Timers = 12 total Timers).

The total test time will be something like:
<timeframe> + <logout timeout> + <time until every session reaches a timer>
By default that will be roughly:
48 minutes timeframe + 2 minutes logout timeout + 4 minutes until a timer = 54 minutes for the overall test.

This all assumes default settings. We recommend a 48 minute (2880) timeframe for all tests, except of course setting things up.

VSI will gradually increase the number of sessions running in your environment. This means that the first session might run for the full 54 minutes while the last session might only run for 4 minutes.

The concept behind the logoff sequence;

Let’s say, You are telling VSI to wait an additional 1800 seconds (30 minutes) before indicating sessions can log off. Set the autologoff timeout back to 120 and sessions will start logging off 2 minutes after the last session has been launched.

This is how it works. Assuming 20 session, 30 second interval and 120 second logoff timeout.
00:00 session 1 is launched. It takes a few seconds to log on and become active.
00:12 session 1 is done logging on, has started the main VSI executable and is now considered active.
00:30 session 2 is launched. It takes a few seconds to log on and become active.
00:44 session 2 is done logging on, has started the main VSI executable and is now considered active.
(these steps repeat up to session 20)
10:00 session 20 is launched. The system is under a reasonable amount of load so log on takes a while. Lets say 50 seconds.
10:01 VSI notices all of the 20 sessions have been launched. It would have indicated to the active sessions that they can start logging off, EXCEPT that there is a autologoff timeout. VSI will wait an additional 120 seconds, the configured autologoff timeout, until indicating session can log off.
10:50 session 20 is done logging on, has started the main VSI executable and is now considered active.
12:01 the autologoff timeout has expired. VSI indicates sessions can start logging off AFTER their current loop is done.
15:12 session 1 is done with its first loop. Session 1 notices VSI has indicated that sessions can start logging off. Session 1 logs off.
15:43 session 2 is done with its first loop. Session 2 notices VSI has indicated that sessions can start logging off. Session 2 logs off.
(etc etc up until all sessions eventually log off)

Lets look at 20 sessions, 30 second interval, 1800 second autologoff timeout.
00:00 session 1 is launched. It takes a few seconds to log on and become active.
00:12 session 1 is done logging on, has started the main VSI executable and is now considered active.
00:30 session 2 is launched. It takes a few seconds to log on and become active.
00:44 session 2 is done logging on, has started the main VSI executable and is now considered active.
(these steps repeat up to session 20)
10:00 session 20 is launched. The system is under a reasonable amount of load so log on takes a while. Lets say 50 seconds.
10:01 VSI notices all of the 20 sessions have been launched. It would have indicated to the active sessions that they can start logging off, EXCEPT that there is a autologoff timeout. VSI will wait an additional 1800 seconds, the configured autologoff timeout, until indicating session can log off.
10:50 session 20 is done logging on, has started the main VSI executable and is now considered active.
(sessions are running and not much happens other than that)
15:12 session 1 is done with its first timer/segment/loop. A loop takes about 48 minutes. Since VSI has not indicated the sessions can start logging off yet session 1 will start another timer/segment/loop.
15:44 session 2 is done with its first timer/segment/loop. Since VSI has not indicated the sessions can start logging off yet session 2 will start another timer/segment/loop.
(this eventually happens for all 20 sessions)
30:12 session 1 is done with its second timer/segment/loop. Since VSI still has not indicated the sessions can start logging off session 1 will start another timer/segment/loop.
30:43 session 2 is done with its second timer/segment/loop. Since VSI still has not indicated the sessions can start logging off session 2 will start another timer/segment/loop.
(this happens for every session that completes a loop up to 40:00)
40:01 the autologoff timeout has expired. VSI indicates sessions can start logging off AFTER their current timer/segment/loop is done.
(some sessions start logging off as their timer/segment/loop finishes)
45:12 session 1 is done with its third timer/segment/loop. Session 1 notices VSI has indicated that sessions can start logging off. Session 1 logs off.
45:43 session 2 is done with its third timer/segment/loop. Session 2 notices VSI has indicated that sessions can start logging off. Session 2 logs off.
(etc etc up until all sessions eventually log off)

Notice how, without the autologoff timeout, session 20 would never become active. That is the idea behind the timeout, allow the last few sessions enough time to log on and become active. Setting the timeout higher and higher just extends the duration of the test.

Let me know if this works for you. Thanks,

Omar.

Please Log in to join the conversation.

  • Raffelstetter
  • Raffelstetter's Avatar Topic Author
26 Jun 2013 15:05 #1214

Hi,
ok i will check my timing settings and test this again.
Thank you for the detailed information!!!

Kind Regards

Please Log in to join the conversation.

Start Delivering the Best End User Experience Today

Request a Demo

Login VSI, Inc.

3945 Freedom Circle
Suite 670
Santa Clara, CA 95054

Phone: +1 408 899 7418

Login VSI B.V.

De Entree 85
1101 BH Amsterdam
The Netherlands

Phone: +31 20 705 1200