We are not observing this on our (busy) sites (running a week or longer).

Can it be that you your application creates mutex objects without destroying it?
In 4.99.12 (Aug 2016) there was a change in NaviServer to provide a more
complete naming of mutexes. Maybe these mutexes just show up because of this?

Is there any reason for not using the released version (4.99.16)?

-g

On 11.05.18 12:40, Wolfgang Winkler wrote:

Hi!

"ns_info locks" returns a lot of entries with names like these:

syncobj:ns:mutex:tcl:151
syncobj:ns:mutex:tcl:150
syncobj:ns:mutex:tcl:149
syncobj:ns:mutex:tcl:148
syncobj:ns:mutex:tcl:147

If the server has been running for a few days, we have millions of entries. A single entry looks like this:

syncobj:ns:mutex:tcl:1383 {} 1903 1 0 0.000000 0.000000 0.000084

ns_info patchlevel: 4.99.16d9
info patchlevel: 8.6.6

regards,

Wolfgang


--
ยด
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel

Reply via email to