http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Esent http://ayende.com/3873/rhino-persistent-hash-table#comment8http://ayende.com/3873/rhino-persistent-hash-table#comment8Wed, 11 Mar 2009 16:01:45 GMTAyende, Where/what is the DHT stored in? http://ayende.com/3873/rhino-persistent-hash-table#comment7http://ayende.com/3873/rhino-persistent-hash-table#comment7Wed, 11 Mar 2009 15:53:47 GMTzfg, what version are you working on? something that I found useful is to change ManagedEsent and make it add additional trace information, such as what table it not being disposed. http://ayende.com/3873/rhino-persistent-hash-table#comment6http://ayende.com/3873/rhino-persistent-hash-table#comment6Mon, 02 Mar 2009 16:37:56 GMTAyende, firstly, thank you for your reply. One thing I should have mentioned in my previous post is that I am already (trying) to dispose the table. I am only using the table inside "using"-statements, so that the IDisposable mechanism kicks in. I also debugged into your overridden Dispose method. So everything seems to be working as intended. Firing up Reflector and having a look at Esent.Interop did show me where the TraceWarning is generated, but did not solve the problem. As I do not think that neither you nor me did write incorrect code (I actually started on this Esent spike in our code using the same syntax like you did in your unit-tests, which - I'm sorry to say - also partly fail on my developer machine with several 'Key duplicates' errors), I'm starting to blame Esent, since the JETTerm call has no effect on the hasResource property on Esent.Interop's side. Lastly, this is no request to you, but if you have any idea, why the EsentResource does not dispose properly (even though the EventLog shows me that Esent instances are getting started/stopped and the database engine is also getting started/shutdown), I'd be very happy to know. On the other side, I may not be using rhino-pht because of the instable behaviour of the Esent (some tests using the same syntax do not trace the warning, even though they are testing the same class and so on), which is kind of sad, since I already thought about moving our project from NServiceBus to Rhino.ServiceBus (which would better match our needs) and we're already using Rhino.Commons and (yes, sadly because we cannot use MVC :( ) Rhino.Igloo for round about one year now. http://ayende.com/3873/rhino-persistent-hash-table#comment5http://ayende.com/3873/rhino-persistent-hash-table#comment5Mon, 02 Mar 2009 12:56:24 GMTzfg, A bug, you are not disposing the table. http://ayende.com/3873/rhino-persistent-hash-table#comment4http://ayende.com/3873/rhino-persistent-hash-table#comment4Fri, 27 Feb 2009 21:19:06 GMTHi Ayende, could you please explain what the following warning is all about: "Warning: 0 : Non-finalized ESENT resource Microsoft.Isam.Esent.Interop.Table" We at our company get this warning during our unit test runs and have not been able to find any explanations in a well-known search engine. http://ayende.com/3873/rhino-persistent-hash-table#comment3http://ayende.com/3873/rhino-persistent-hash-table#comment3Fri, 27 Feb 2009 16:12:24 GMTpb, Rhino DHT is not a cache. It can be _used_ as one, most certainly, but it isn't one. The data is persistent, replicated and fail over. And yes, I am currently going with it to production. http://ayende.com/3873/rhino-persistent-hash-table#comment2http://ayende.com/3873/rhino-persistent-hash-table#comment2Sun, 15 Feb 2009 03:00:03 GMTWhat would you say the major differences are between Rhino DHT and MS velocity, ncache or shared cache. Is it in anything resembling a production usuable state and if not how long do you think it will be until it is? http://ayende.com/3873/rhino-persistent-hash-table#comment1http://ayende.com/3873/rhino-persistent-hash-table#comment1Sun, 15 Feb 2009 02:34:27 GMT