Re: [WebDNA] SQLExecute Memory Leak
This WebDNA talk-list message is from 2008
It keeps the original formatting.
numero = 100420
interpreted = N
texte = --=====================_17900250==.ALTContent-Type: text/plain; charset="us-ascii"; format=flowedHello Sarah:I checked the revision list at:http://webdna.smithmicro.com/ref/WebDNA%20Change%20History.htmlThere is a notice of a memory leak that was fixed with version 4.5.1.6/15/2002 4.5.0 * Bug Fixes * All Platforms: * Fixed a memory leak with the database cache code. High volume site would be most affected by the memory leak, as it only occured when more than one thread required access to the same database at the same time.Thank you,Greg.At 03:53 PM 7/29/2008, you wrote:>Hi,>>We have been using Webdna for a few years now. At least twice a day >the DBServer.exe memory gets sky high. "WebCatalog does not have >enough memory to complete this command" is logged to the >errorlog.txt, and the service needs to be restarted.>>We were able to narrow one of the issues to the SQLExecute >statements that we use. With every query made the memory climbs, and >does not go down once the query has been completed.>>Has anyone else found this to be an issue?>>We are using a Mysql Database (version 4.1.20). The Web server is >running Windows 2003. We are using WebDNA version 6.1.>>Thanks!>--=====================_17900250==.ALTContent-Type: text/html; charset="us-ascii"Hello Sarah:
I checked the revision list at:
http://webdna.smithmicro.com/ref/WebDNA%20Change%20History.htmlThere is a notice of a memory leak that was fixed with version4.5.1.
6/15/2002 4.5.0
All Platforms: - Fixed a memory leak with the database cache code. High volume sitewould be most affected by the memory leak, as it only occured when morethan one thread required access to the same database at the same time.
Thank you,
Greg.
At 03:53 PM 7/29/2008, you wrote:
Hi,
We have been using Webdna for a few years now. At least twice a day theDBServer.exe memory gets sky high. “WebCatalog does not have enoughmemory to complete this command” is logged to the errorlog.txt, and theservice needs to be restarted.
We were able to narrow one of the issues to the SQLExecute statementsthat we use. With every query made the memory climbs, and does not godown once the query has been completed.
Has anyone else found this to be an issue?
We are using a Mysql Database (version 4.1.20). The Web server isrunning Windows 2003. We are using WebDNA version 6.1.
Thanks!
--=====================_17900250==.ALT--
Associated Messages, from the most recent to the oldest:
--=====================_17900250==.ALTContent-Type: text/plain; charset="us-ascii"; format=flowedHello Sarah:I checked the revision list at:http://webdna.smithmicro.com/ref/WebDNA%20Change%20History.htmlThere is a notice of a memory leak that was fixed with version 4.5.1.6/15/2002 4.5.0 * Bug Fixes * All Platforms: * Fixed a memory leak with the database cache code. High volume site would be most affected by the memory leak, as it only occured when more than one thread required access to the same database at the same time.Thank you,Greg.At 03:53 PM 7/29/2008, you wrote:>Hi,>>We have been using Webdna for a few years now. At least twice a day >the DBServer.exe memory gets sky high. "WebCatalog does not have >enough memory to complete this command" is logged to the >errorlog.txt, and the service needs to be restarted.>>We were able to narrow one of the issues to the SQLExecute >statements that we use. With every query made the memory climbs, and >does not go down once the query has been completed.>>Has anyone else found this to be an issue?>>We are using a Mysql Database (version 4.1.20). The Web server is >running Windows 2003. We are using WebDNA version 6.1.>>Thanks!>--=====================_17900250==.ALTContent-Type: text/html; charset="us-ascii"Hello Sarah:
I checked the revision list at:
http://webdna.smithmicro.com/ref/WebDNA%20Change%20History.htmlThere is a notice of a memory leak that was fixed with version4.5.1.
6/15/2002 4.5.0
All Platforms: - Fixed a memory leak with the database cache code. High volume sitewould be most affected by the memory leak, as it only occured when morethan one thread required access to the same database at the same time.
Thank you,
Greg.
At 03:53 PM 7/29/2008, you wrote:
Hi,
We have been using Webdna for a few years now. At least twice a day theDBServer.exe memory gets sky high. “WebCatalog does not have enoughmemory to complete this command” is logged to the errorlog.txt, and theservice needs to be restarted.
We were able to narrow one of the issues to the SQLExecute statementsthat we use. With every query made the memory climbs, and does not godown once the query has been completed.
Has anyone else found this to be an issue?
We are using a Mysql Database (version 4.1.20). The Web server isrunning Windows 2003. We are using WebDNA version 6.1.
Thanks!
--=====================_17900250==.ALT--
Greg Kesler
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
RE: Displaying Location (1997)
[WebDNA] [WSC] WebDNA Development Summit (2014)
[WebDNA] WebCatalog process dies (2012)
unable to launch acgi in WebCat (1997)
Context and commands (1998)
Date or time comparisons have bugs ... (1998)
credit card (1997)
Counting Inventory (2003)
Director 7 (1999)
Location of Browser Info.txt file (1997)
Re:2nd WebCatalog2 Feature Request (1996)
Authenticate (1997)
I give up!! (1997)
I'm new be kind (1997)
[ModDate] & [ModTime] ? (1997)
Avery 5160 Mailing Labels (2003)
Discounting prices across a site (1997)
Pithy questions on webcommerce & siteedit (1997)
Moment of Thanks (1997)
Emailer problems addition (1999)