No problem, you are simply confirming that you are talking about an
application-specific cache that has nothing to do with IIS -- so you
probably won't find the answer in this newsgroup.  You will have to follow
up with the appropriate application support concerning the cache's behavior.
I suggest either www.asp.net Forums or the ASP.Net newsgroup.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Karsten" <Karsten@discussions.microsoft.com> wrote in message
news:FEDD49A7-6FA0-497F-B32E-B49D8943783F@microsoft.com...
"David Wang [Msft]" wrote:

> You will want to look for help specific to the particular custom caching
> construct.  It doesn't sound like anything to do with IIS because:
> 1. There is no IIS Application Pool Cache

so which cache is used if a cache.insert within asp.net is thrown to iis?

> 2. No IIS cache survive a recycle.

but there is no recycle, the elements just dosent stay in cache(only for
seconds) and for me it seems the memory is still at its limit...only a
manuel
recycle lets the new elements stay

...i hope iam not confusing you 

> --
> //David
> IIS
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> //
> "Karsten" <Karsten@discussions.microsoft.com> wrote in message
> news:86F197E1-7275-4F7B-8809-BA5DF2E9CE5D@microsoft.com...
> i think its the ASP.NET Application cache. now i have set the limit of max
> used mb up to 1200 mb and it seems to work. but i still have no feeling of
> being right!
> at this server there are 180 webs within one apllication pool
>
> "David Wang [Msft]" wrote:
> 
response[vbcol=seagreen] 
> rights. 
if[vbcol=seagreen] 
stay[vbcol=seagreen]
> in 
> changed, 
will[vbcol=seagreen] 
no[vbcol=seagreen] 
> cache 
>
>
>

[ Post a follow-up to this message ]