G
Guest
Last month we upgraded our production server from .net 1.1 to 2.0. We have
seen some odd behaviour that we do not know how to fix.
It seems that Cache is reset or cleared. We have 2 or 3 global entries in
the the cache with the NotRemovable flag set. I have set up a callback that
writes an entry to the event log to see if the Cache is cleared. It appears
that it is. This happens (randomly) several times a day. I changed our global
entries to use Application state however this just seemed to amplify the
problem.
Could this be a bug with 2.0 or does a server setting need changing
somewhere (it is a windows 2003 server)?
I do not know if the cache is being reset, causing the application to crash,
or something is causing the application to crash, resulting in the cache
being reset (I have added the LegacyUnhandledExceptionPolicy enabled="true"
attribute to the web.config with no joy)
At the same time that an entry is written to say the cache has been cleared,
the performance monitor registers requests /second at 286,000,000
If anyone has experienced similar issues, can shed some light or point me in
the right direction it would be greatly appreciated.
Kind Regards,
Darren
seen some odd behaviour that we do not know how to fix.
It seems that Cache is reset or cleared. We have 2 or 3 global entries in
the the cache with the NotRemovable flag set. I have set up a callback that
writes an entry to the event log to see if the Cache is cleared. It appears
that it is. This happens (randomly) several times a day. I changed our global
entries to use Application state however this just seemed to amplify the
problem.
Could this be a bug with 2.0 or does a server setting need changing
somewhere (it is a windows 2003 server)?
I do not know if the cache is being reset, causing the application to crash,
or something is causing the application to crash, resulting in the cache
being reset (I have added the LegacyUnhandledExceptionPolicy enabled="true"
attribute to the web.config with no joy)
At the same time that an entry is written to say the cache has been cleared,
the performance monitor registers requests /second at 286,000,000
If anyone has experienced similar issues, can shed some light or point me in
the right direction it would be greatly appreciated.
Kind Regards,
Darren