Re: Out-of-process State Management Session Cleanup



Thanks for the help so far, here is some more information about the
situation that is giving us a hard time.

We have data being stored in the session that must be transmitted
externally via HTTP (Web Services Call). If the user ends the process
normally, the session-stored information can be controlled and will be
sent correctly. If the session times out, we want what has been stored
so far in the session to be sent. This is where our problem occurs.

By converting to the out-of-process state management there is no way
of .NET knowing when the the session has ended, or when the session
information is cleared. Therefore, the information that must be sent
is never sent and is lost forever.

Is there any way of alerting the .NET application that the session is
being cleared by the SQL Server (Stored Procedure)? Or are there any
other methods that are possible in this particular solution?

Keep in mind that this could be in a web farm, so there is not really
any way of knowing which process is currently in charge of the session
data.

Thanks again,
Marc


On Sep 11, 5:39 pm, knyghtf...@xxxxxxxxx wrote:
Hello,

My company is developing a rather large application with .NET 2.0. We
are expanding to a server farm and are in the process of converting
our application to use an out-of-process session state management with
SQL Server.

We have ran into a problem with the Session_onEnd event. We know it's
not supposed to fire when in an out-of-process mode, but we have a
large amount of code that must be executed to clean the session and to
log some critical data.

Are there any best practises for dealing with such a situation? What
have others done in the past that have helped them keep a session
state that times-out and cleans up afterwards? Is there a possibility
of the SQL Server to keep track of said timeout and execute some clean
up code?

I've been searching for a few days now and have not yet been able to
find any "best practises" for this type of situation, if you know of
any articles, or have any personal experience, any help is
appreciated.

Thanks,
Marc


.



Relevant Pages

  • Re: Best way to populate webpages from multiple tables
    ... tables within hash tables, custom classes etc. ... > Set a session expiring cookie at the client that stores the Customer ID. ... > send it to the client, instead store it in your session mgmt sql server - ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Best way to populate webpages from multiple tables
    ... tables within hash tables, custom classes etc. ... > Set a session expiring cookie at the client that stores the Customer ID. ... > send it to the client, instead store it in your session mgmt sql server - ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Out-of-process State Management Session Cleanup
    ... How critical is the last log on session info to the new login session for ... large amount of code that must be executed to clean the session and to ... state that times-out and cleans up afterwards? ... of the SQL Server to keep track of said timeout and execute some clean ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Failover causes General network error in ASP.NET
    ... I've removed all session and database code from the ASP.NET test ... control over detecting whether the SQL Server connection is available. ... > If you want total transparent failover, you will have to wait for Database ... >> I've built an Active/Passive cluster with two nodes, ...
    (microsoft.public.sqlserver.clustering)
  • Session management on web farm with sql server
    ... it experiences some strange problems when run on a web farm using SQL Server ... In this example the object is pulled out of session, ... AppDomain and a reference is created for the session. ...
    (microsoft.public.dotnet.framework.aspnet)