0

I face a problem on my wcf service running under IIS with object called TimeBoundedCache+ExpirableItem under System.ServiceModel.Security. I investigate these object and see its they exsists on the Gen2 for long time and my wcf memory is growing up .

I see there is a 48 hours expiration time of these objects . How can clean these objects, or maybe shorten the expiration time .

Thanks in advance ...

Wasim
  • 1,915
  • 5
  • 24
  • 39
  • so are you sure that it is these objects that are causing your growing memory? The fact that objects live for a long time in gen 2 is normally a good thing - cleaning up garbage in gen2 is expensive. If you're getting a new long lived object for each request on the other hand is bad -can you add what binding you are using and whether your clients close their proxies? – Richard Blewett May 13 '12 at 12:05
  • Thanks for the reply . The binding I use is wsHttpBinding , wiht message security . Also I close the client after the call. The problem this memory is growing up, thats mean I I don't make a recycle to the IIS pool the service will arrive high memory level. – Wasim May 14 '12 at 06:06

0 Answers0