More ASP.NET Sessions than I can handle!

[Don Bouchard]

I am having a very strange problem with VB.NET 2003 on a
WinXP SP1 system. I am developing an ASP.NET app with
multiple web pages. I create a session level hash table
(indexed by session.sessionid) to store user specific
info. My login function stores the data happily, but
when I went later on in my app to retrieve my data, it
wasn't there. I finally discovered that the sessionId my
app had when it put the data in the hashtable was not the
same sessionId as when I went to get it, thus the cause
of my access problem.

Further debugging led me to discover that I was getting
multiple sessions being created during my app. I
confirmed this by adding a Beep() function in my
project's GLOBAL.ASAX.VB \ Session_Start subroutine. It
sounds like a machine gun of sessions being created when
I run my app!

I keep on thinking it is some session timeout setting,
but I think my web.config is clean and so is my
machine.config file. Any thoughts, ideas or places to
check?

Thanks very much!

[Armin Zingler]

"Don Bouchard" <db*******@tricomputer.com> schrieb

I am having a very strange problem with VB.NET 2003 on a
WinXP SP1 system. I am developing an ASP.NET app with
multiple web pages. I create a session level hash table
(indexed by session.sessionid) to store user specific
info. My login function stores the data happily, but
when I went later on in my app to retrieve my data, it
wasn't there. I finally discovered that the sessionId my
app had when it put the data in the hashtable was not the
same sessionId as when I went to get it, thus the cause
of my access problem.

Further debugging led me to discover that I was getting
multiple sessions being created during my app. I
confirmed this by adding a Beep() function in my
project's GLOBAL.ASAX.VB \ Session_Start subroutine. It
sounds like a machine gun of sessions being created when
I run my app!

I keep on thinking it is some session timeout setting,
but I think my web.config is clean and so is my
machine.config file. Any thoughts, ideas or places to
check?

Thanks very much!

Looks like an ASP.NET problem, not like one specific to VB.NET. Please turn
to microsoft.public.dotnet.framework.aspnet[.*]
--
Armin