On Thu, Jan 23, 2003 at 07:23:28PM -0500, Seena wrote: > After setting up a new server (AOLserver 3.3.1 w/ TCL 8), it seems using > the "ns_mutex" to luck array/list, while serve is running, bring our site > down. The same setup and code/application with AOLserver 2.3.3 w/ TCL 7, > works fine. Any comment why/how this is happening ? > > I've heard we can use ns_rwlock instead of ns_mutex, would anyone recommand > replacing ns_mutex with ns_rwlock ?
I've used ns_mutex pretty heavily with AOLserver 3.3+ad13 and Tcl 8.3.2 on Solaris, and I've never had any problems. If your nsd process is dieing, you must have something broken in your AOLserver, although I've no idea what. Perhaps someone else here will, so you should probably post a lot more details: Where you got your AOLserver code, how you compiled it, what operating system, etc. I've never used ns_rwlock, so I don't know abou that. What exactly are you using ns_mutex for? Are you using ns_share? Perhaps you could avoid having to use ns_mutex at all by using nsv? Or are you doing something that you REALLY need to us ns_mutex for, like using ns_cond, or making several separate nsv operations atomic? Also, you said this problem "brings your site down", but in the subject you said AOLserver is "hung"? What exactly is the failure mode? Is your nsd process segfaulting? Or are you just deadlocking threads such that AOLserver hangs there doing nothing? -- Andrew Piskorski <[EMAIL PROTECTED]> http://www.piskorski.com
