Problem in console application using Caching Application Block

  • Thread starter Thread starter ams8764
  • Start date Start date
A

ams8764

I am facing a problem with a .NET console application that uses the
Caching Application Block from Enterprise Library June 2005.

Since I have added the use of the caching block, I have sometimes (!)
the following behaviour : the console application does not end but
stays idle (no memory consumption, flat CPU usage). I cannot end it
with CTRL+Z, I have to kill the DOS box or kill the process.

This does not happen all the time, but approximatively one in ten
times.

I am writting to the Console output at the very end of the static main
method, so I know there isn't any processing occuring anymore, and that
the program is not within my own code when it stays idle.

I am using the caching block "null storage" mode.
The program works fine, cache data is correctly accessed and managed,
it just won't return.

Is there any known issue when using the Caching application block in a
console application ?

Platform details :
- Windows 2000 Advanced Server (Fully patched)
- .Net v1.1.4322
- tests made using Remote Desktop Connection

Thanks a lot in advance for your help,

AMS
 
My blind guess is that the scavenging thread does not terminate
automatically. May be you need to request scanvenging process termination
manually, please refer to the application block documentation for more
detail.
 
Back
Top