What can cause the value in Application variable to disappear?

[evangeline]

We have ASP application running on IIS 5.1 and Windows 2000 server. The ASP
application has few Application variables setup in global.asa. Something like
this:
Application.Loc k()
Application("fu n")="play"
Application.UnL ock()

There is no other code in the ASP application to change the value in the
Application variables. It's only set in global.asa and the rest of the
application just read it with code similar to this:
Response.Write( Application("fu n"))

The application had been running fine until we deployed a COM DLL to the web
server few weeks ago. Loos like the ASP application started to loose the
value in application variable few times a day. Restarting the web service,
which means re-initialize the value in Application object, fixes the issue
but the value will be blanked out again after few hours.

The COM DLL is written in .Net C# to handle some task. This COM has "private
static" variables in public class. The purpose for "private static" variables
is that the value will be maintained until IIS is restarted.

Is it possible that the memory space for .Net run-time conflicts with the
memory space of ASP Application object? Can someone help me understand what
can cause this to happen?

Thanks a lot!!

[Bob Barrows [MVP]]

evangeline wrote:

We have ASP application running on IIS 5.1 and Windows 2000 server.
The ASP application has few Application variables setup in
global.asa. Something like this:
Application.Loc k()
Application("fu n")="play"
Application.UnL ock()

There is no other code in the ASP application to change the value in
the Application variables. It's only set in global.asa and the rest
of the application just read it with code similar to this:
Response.Write( Application("fu n"))

The application had been running fine until we deployed a COM DLL to
the web server few weeks ago. Loos like the ASP application started
to loose the value in application variable few times a day.
Restarting the web service, which means re-initialize the value in
Application object, fixes the issue but the value will be blanked out
again after few hours.
I would rather create a page that does what you do in the
application_ons tart event in global.asa. If the variable is empty, use
Server.Execute to run that page instead of throwing an error, or whatever
consequence is happening to cause you to restart your application.

The COM DLL is written in .Net C# to handle some task. This COM has
"private static" variables in public class. The purpose for "private
static" variables is that the value will be maintained until IIS is
restarted.

Is it possible that the memory space for .Net run-time conflicts with
the memory space of ASP Application object? Can someone help me
understand what can cause this to happen?

I've never seen anything like this. Sorry.

Bob Barrows

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

[GermanK.Net]

I'm having the same problem with ASP 3.0 & IIS 5.0, but it's related
only to application variables containing multidimensiona l arrays. It's
very strange, it happens randomly during high & low server load time...

Anybody knows anything about it?

Thanks
Germán Kondolf
System Architect .Net

Bob Barrows [MVP] ha escrito:

evangeline wrote:

We have ASP application running on IIS 5.1 and Windows 2000 server.
The ASP application has few Application variables setup in
global.asa. Something like this:
Application.Loc k()
Application("fu n")="play"
Application.UnL ock()

There is no other code in the ASP application to change the value in
the Application variables. It's only set in global.asa and the rest
of the application just read it with code similar to this:
Response.Write( Application("fu n"))

The application had been running fine until we deployed a COM DLL to
the web server few weeks ago. Loos like the ASP application started
to loose the value in application variable few times a day.
Restarting the web service, which means re-initialize the value in
Application object, fixes the issue but the value will be blanked out
again after few hours.

I would rather create a page that does what you do in the
application_ons tart event in global.asa. If the variable is empty, use
Server.Execute to run that page instead of throwing an error, or whatever
consequence is happening to cause you to restart your application.

The COM DLL is written in .Net C# to handle some task. This COM has
"private static" variables in public class. The purpose for "private
static" variables is that the value will be maintained until IIS is
restarted.

Is it possible that the memory space for .Net run-time conflicts with
the memory space of ASP Application object? Can someone help me
understand what can cause this to happen?

I've never seen anything like this. Sorry.

Bob Barrows

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"