On Thursday, January 10, 2002, at 03:56 PM, David Walker wrote: > What about using Ns_ConnClose in a scheduled proc that runs every x > minutes > (or x/2 minutes) and closes conns that have exceeded their time limit? That would free up the connections so they can be reused, but if you've got a thread blocked on some resource, or spinning in a computation of some sort, the block/spin will go on. Thinking about this, it seems to me that the thread for the conn wouldn't be released, either, so you'd shut down the connection, but the thread wouldn't be killed.
If you've got a blocked resource, you've got a prayer of sending the AOLserver process some signal that might break it, if, for example, the block is waiting for a select() or something; if it's waiting on a mutex, you're pretty much toast.
