469,609 Members | 1,166 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,609 developers. It's quick & easy.

Potential bug: ASP.NET session variables and file watcher service

Hi

I have an interesting issue, I hope someone can shead light on:

I have a 2 server "web farm" with a web app that produces image files. To
ensure synchronization of content on both machines, we have built a vb.net
(2.0) file watcher service to keep the web folders synchronized between the 2
machines. the app uses in-proc session variables for some other stuff.

We have run into a strange problem: when the file watcher service is
running, the session variables seem to die and we lose the "context" we have
created for the user when they login. We have ensured that the file wather
works on directories that do NOT contain code files (aspx). However, the
directories are virtual directories on the respective sites. The session
variables are holding a hashtable of complex types (db connections, command
objects etc).

The file watcher (FW) app seems to work just fine. If we turn the FW off,
the session variables do not die!@#!@#!!

I know this isn't an enormous amount of detail, but is there anything that
we should be aware of here? what would help to illuminate the problem? The
code for each is way to big to post.

Some background: using .NET 2.0, vb for both apps. Windows 2003 std Server
(sp1) and IIs 6.0.

thx
Avi
May 21 '07 #1
1 2536
Howdy,
AppDomain restarts:
http://objectsharp.com/cs/blogs/bruc...11/01/992.aspx

The session
variables are holding a hashtable of complex types (db connections, command
objects etc).
OMG! :)

Hope this helps
--
Milosz
"Avi" wrote:
Hi

I have an interesting issue, I hope someone can shead light on:

I have a 2 server "web farm" with a web app that produces image files. To
ensure synchronization of content on both machines, we have built a vb.net
(2.0) file watcher service to keep the web folders synchronized between the 2
machines. the app uses in-proc session variables for some other stuff.

We have run into a strange problem: when the file watcher service is
running, the session variables seem to die and we lose the "context" we have
created for the user when they login. We have ensured that the file wather
works on directories that do NOT contain code files (aspx). However, the
directories are virtual directories on the respective sites. The session
variables are holding a hashtable of complex types (db connections, command
objects etc).

The file watcher (FW) app seems to work just fine. If we turn the FW off,
the session variables do not die!@#!@#!!

I know this isn't an enormous amount of detail, but is there anything that
we should be aware of here? what would help to illuminate the problem? The
code for each is way to big to post.

Some background: using .NET 2.0, vb for both apps. Windows 2003 std Server
(sp1) and IIs 6.0.

thx
Avi
May 21 '07 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by Marcelo López | last post: by
3 posts views Thread by Ron Vecchi | last post: by
4 posts views Thread by Marcelo López | last post: by
2 posts views Thread by Jack David | last post: by
2 posts views Thread by John Lee | last post: by
3 posts views Thread by Mark | last post: by
3 posts views Thread by bennett | last post: by
reply views Thread by devrayhaan | last post: by
reply views Thread by gheharukoh7 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.