i have a problem with a web farm. an application asp net 1.1 that works
in different servers.doesnt works in the web farm (4 servers balanced). The error it says is
"System.Web.HttpCompileException: External component has thrown an exception"
basically is a page that its requested in one server and served by other
server and are different version of the application
.. the technichal staff says its applied the same version in the four servers
and i can believe them.
Is it possible to use session in web farm? Some say just use cookies because
session does not work in web farm. But others say something about persist
into SQL Sever, if this is true please tell me more about this approach.
I will soon be undergoing a project where I will be migrating four to five web applications, developed in classic ASP, from a single Windows Server 2000 to a web farm that will utilize two, Windows 2003 Servers.
All of the applications utilize user/session management and I know that ASP's built-in session management cannot be carried across multiple servers.
I've been researching products available for purchase out there on the web, which allows you to include new code, which overrides ASP's built-in session management, by using a database to store sessions.
They all advertise that their solutions simply require just one line of code to be added to each ASP pages that uses Sessions, without any other changes to the existing ASP code.
Can someone who has done something similar advise on their experience? Is this really as easy as they are advertising, or are there other issues to take into consideration? Code:
Im using classic ASP (3.0) and I have a web farm with 2 webservers
(webserver A and webserver B, both windows server 2003). I do not want
to store any client specific information on the webserver (therefore do
not intend to use the session object- as you cannot gaurantee which
server the user will go to). I want to store a small value (e.g. a Y/N
value or an Id) on the client machine for the duration of their
browsing session, hence I want to use a non persistent cookie (in
client memory) not a persistent cookie that will be written to disk as
a file.
Q. Therefore if I create a non persistent cookie (i.e. it resides in
the client browsers memory) and set this when the user was on webserver
A, can I read the value server side on subsequent requests even if the
user is redirected back to webserver B? As the webservers are part of
the same domain name Im assuming I can..?
Q. Using non persistent cookies (in client in memory) im assuming the
session Id that gets created by IIS has no use, as I am using client
side storage, hence it is worth disabling this on the webserver for
performance reasons?
Q. Is there a way, when using non persistent cookies that the client
user can see the values of this cookie client side, are their any
downloadable tools for example they can run?
Im aware of the issues with size of using cookies and users can disable
them, my question is more related to using them in a web farm. Im also
not intended in the short term to upgrade to asp.net as Im aware there
are alternatives for state storage in this. I hope someone can clarify
these points for me. Note: I see many articles talking about cookies
but none relating to web farms and cookies, those that do talk solely
about the session object (Server side), none really go further to talk
about (non persistent / persistent cookie usage with web farms client
side.