Hi,

I have noticed that the 2nd level SysCache is not always working when I am debugging using Visual Studio 2005...has anyone else noticed this? I can see that my app is running visibly slower and when I run SQL profiler I can see all the activity against the DB despite the fact that I have the cache fully enabled.

The strange this is that in other instances of debugging, with exactly the same app, I can see that the cache is operating fully as expected with no hits to the DB.

Obviously, this is not a major issue as I am only debugging, but it is strange nevertheless!

Cheers,

Jason

Actually, it seems that the SysCache stops working entirely as soon as the development web server is running...even for websites that are hosted in IIS! Not sure if this is specific to NH though as it could be a problem in general with SysCache.

I am having a very similar issue... however, I am not sure if it is only isolated to debugging.

Basically, I see NHibernate cache my entities, but they are never there when I go for subsequent lookups. The logs show me that the object is materialized and placed into the cache at a particular region, but directly after that it appears that the entire session factory is reloaded.

Any Ideas?

So I have confirmed that this is the case with VS 2005 in Debug mode: After some period of time / memory consumption the entire NHibernate session factory is rebuilt (visible via the logging of the configuration reload). At that point, the cache is cleared, obviously... but also from that point forward the cache will not work - items stored in the cache are almost immediately removed (but what process, I don't know). I have even witnessed more session factory reloads from that point on.

Any ideas?

I'm trying to find out whether entities are persisted into Cache (currently using SysCache)?

Everytime I try to query for an entity based on Criteria it always does a new Database fetch (based on SQL from the Log file).

Is there anyway to view all the entities persisted in Cache?

Thanks for all the help guys

Criteria queries are stored in the Query Cache... so ensure that you are using the "setCacheable(true)" and "setCacheRegion(...)" methods when you create your query. Also, you must have a matching cache region defined in your web.config file under the <syscache> section.

Finally, you can alway interrogate the ASP Cache to see what is in it if you are using SysCache.

HTH,
Aaron

thanks Aaron

I'll try and come back to you