Re: [AOLSERVER] Database handles not being released in 4.0
On Wednesday, March 26, 2003, at 10:15 PM, paul cannon wrote: So http://aolserver.com/docs/devel/tcl/api/db.html is at best misleading: ns_db releasehandle puts the handle back in the pool. When your operation has finished running, the server will automatically return any handles to their pools, so you don't normally have to call this function. I may have misunderstood the meaning of operation. No, I think you have it right. I never noticed this, and I just checked and it was in the 2.x docs. That'll teach me not to read the docs carefully enough. In my opinion, it's a bug. You should file it in SourceForge. At this point, I think my superstition about not trusting AOLserver to clean up the handles is probably still appropriate. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Database handles not being released in 4.0
On Wednesday, March 26, 2003, at 07:59 PM, paul cannon wrote: It seems that when a database handle is allocated in an ADP page and not explicitly released, AOLserver no longer releases it automatically. Is this true? If so, I can't find any documentation anywhere that would suggest this is the case. Way back in the 2.x days, I moved an app from Illlustra to Sybase, only to discover that the automatic handle cleanup that happened in Illustra wasn' t happening in Sybase. MarkD helped get that working for Sybase, and I learned that automatic handle cleanup was, in the 2.x days, database-driver-dependent. I think the bottom line is that there is not documentation that says AOLserver will clean up database handles that aren't explicitly released, so you should not depend on the feature. catch is your friend. Also, this is one of the things about the current adp processing model that's nice, because you can have a script chunk at the end of the page that says if the variable that holds the handle is non-empty, release it, and it will be executed, even if script chunks earlier in the page up-and-die. Pete. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Database handles not being released in 4.0
On Wed, Mar 26, 2003 at 08:56:52PM -0500, Peter M. Jansson wrote: I think the bottom line is that there is not documentation that says AOLserver will clean up database handles that aren't explicitly released, so you should not depend on the feature. So http://aolserver.com/docs/devel/tcl/api/db.html is at best misleading: ns_db releasehandle puts the handle back in the pool. When your operation has finished running, the server will automatically return any handles to their pools, so you don't normally have to call this function. I may have misunderstood the meaning of operation. catch is your friend. Also, this is one of the things about the current adp processing model that's nice, because you can have a script chunk at the end of the page that says if the variable that holds the handle is non-empty, release it, and it will be executed, even if script chunks earlier in the page up-and-die. Agreed. -- .. | paul cannon [EMAIL PROTECTED] | | operation misserhttp://people.debian.org/~pik/ | -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
