From: Vlad S. <vl...@cr...> - 2006-06-05 21:23:30
|
Definitely, i just recompiled NS on working server with recent version and started crashing on ns_cache. This is the showstopper. Zoran Vasiljevic wrote: > Am 05.06.2006 um 04:36 schrieb Vlad Seryakov: > >> Current cache implementation in naviserver is somewhat broken because >> with recent version i cannot run my app under ns_cache_ and event with >> old ns_cache module as well, i have crashes inside C level cache API, >> but i use only Tcl api. Something was changed that influenced even >> ns_cache because it used underlying C level cache of the core. >> >> My app uses simple caches, just ns_cache eval, the difference that >> this >> is Network management system and it runs many many threads at the same >> time using ns_job, so i am guessing that concurrency is what kills. It >> works on older versions of NS 4.99.0|1 and AOL 4.0 using ns_cache, i >> tried to convert it to internal ns_cache_family but it does not >> work, it >> hangs indefinitely, but works with ns_cache up until CVS version. > > I also think it is the concurrency as I regulary have problems > (which I already described) and cannot point my finger at any > place. Simulating trouble-cases is also not simple (haven't got > the chance to do that), yet my application regulary breaks. > > In my case, it is not crashing, rather error due to timeouts > waiting for lock which normally should not exist. > > I think this will not be easy... > > Cheers > Zoran > > > _______________________________________________ > naviserver-devel mailing list > nav...@li... > https://lists.sourceforge.net/lists/listinfo/naviserver-devel > -- Vlad Seryakov 571 262-8608 office vl...@cr... http://www.crystalballinc.com/vlad/ |