We are using several NLB clusters with W2k Advanced and/or Application Center 2000 without problems. Keep in mind that only the "Single Call" is really fully supported in an NLB environment. Also don't forget to lower the "HTTP Keep Alive" configuration, with the default value of 900 seconds we saw that the connections are keep from the remoting client and not really doing an even balancing of the work. The result of an high keep alive is some "client affinity", something not desired in an NLB environment.
Best regards, Andr�s G Vettori MCSE/MCSD/MCT Thawte Notary [EMAIL PROTECTED] Phone +54(11) 15-4914-2560 Obten� tu certificado digital totalmente gratis en http://www.thawte.com/getinfo/programs/wot/about.html -----Original Message----- From: Moderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED]] On Behalf Of Vikram Srivatsa-SRIVDGS Sent: Thursday, December 19, 2002 1:21 PM To: [EMAIL PROTECTED] Subject: Re: [ADVANCED-DOTNET] .NET Remoting In a Clustered Environment. Hi Justin, Thanks for the info. So, If I go with NLB instead of MSCS I should not face any problems ?? Also, is this a problem with MSCS and IIS or is it MSCS, IIS and .NET... I mean is it a sepcific problem with .NET ?? In case I went on MSMQ can I do some synchronous operations as well ?? Would there not be a latency ? Thanks, Vikram -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 17, 2002 4:27 PM To: [EMAIL PROTECTED] Subject: Re: [ADVANCED-DOTNET] .NET Remoting In a Clustered Environment. MS has always recommended against clustering IIS in MS Cluster Server, and if you intend on using IIS to host your remote objects, you may experience some issues. Specifically, installing the .Net Framework breaks the IISSYNC application that is used to replicate IIS metadata between cluster nodes before clustering IIS. Breaks it badly enough that running IISSYNC in the broken state corrupts the metadata so badly that a re-install of IIS is required. This is not a terribly fun process ;) This is the only real issue I have seen with respect to MSCS and .Net. <geekMode> How asynchronous? Would MSMQ solve that particular bit? MSMQ can be clustered. MSMQ Triggers can invoke .Net applications / COM+ wrapped .Net assemblies.</geekMode> --------------------------- Justin E. Pitts, Sr Programmer Analyst PC Applications Development BIG LOTS -- World's Best Bargain Place 614 278-3255 Vikram S <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Sent by: "Moderated cc: discussion of advanced Subject: [ADVANCED-DOTNET] .NET Remoting In a Clustered Environment. .NET topics." <[EMAIL PROTECTED] EVELOP.COM> 12/16/2002 06:39 PM Please respond to "Moderated discussion of advanced .NET topics." Hi, I am planning to use .NET Remoting for transfering data between client and server in an asynchronous way. Since the application needs to be highly available, we will be using a Win2k Cluster with fail-over. Are there any issues in using .NET Remoting with any particular type of cluster ?? Thanks, Vikram You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
