Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

app issue?

Status
Not open for further replies.

affank

MIS
Joined
Sep 13, 2004
Messages
4
Location
US
We have a Citrix farm that has 3 XPe 1.0 FR3 Servers using Windows 2003 Server. They are configured the same and plus we are using Load balancing. Anyways here is my issue let say a user logs on opens up word and the app launches on server 1. Then few minutes later that same user launches another app like Outlook and that app opens up on Server 2. Why does it do that? If we try to open another app it will jump to Server 1 again.

I thought when a person logs on to a server (in our case the Server 1) each time he wants to open another new app he would stay connected to that original server instead of moving around the farm.

Any help would be appreciated.

Thanks
 
I would check the load balancing logic behind your serversystem. But anyway it seems logic to me. Load balancing is about giving the status of your farm at this very moment, right? So, the fact that server 1 had the best capacity when you opened app1, does not mean that server 1 is the preferred server at the moment the user opens app2. But the key here is to look at the load balancing rules. What do they tell you?
 
affank,
This is not an app issue or a load balancing issue.
When you publish out single apps like word, excel, outlook, powerpoint..etc.etc; it's not guaranteed that they will launch on the same server as the 1st session.
The second session will try to launch it on the same server as the current session BUT if the server is busy or has hit its load evaluator threashold...it will fire it up on the 2nd server. Remember, this is a load-balanced application so it will look at the server that's least busiest. One thing I would do is crank up the load evaluator as high as you possibly can. In this case the server would have to be really really busy to fire the app on the second server.
Hope that helps!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top