RE: [WebDNA] SQLExecute Memory Leak
This WebDNA talk-list message is from 2008
It keeps the original formatting.
numero = 100421
interpreted = N
texte = This is a multi-part message in MIME format.------=_NextPart_000_003A_01C8F1C4.6429BC80Content-Type: text/plain;charset="us-ascii"Content-Transfer-Encoding: quoted-printableBut I am using a later version (6.1). I assume that the problem would =havebeen resolved for this version.=20=20 _____ =20From: Greg Kesler [mailto:gregk@clarityconnect.com]=20Sent: Tuesday, July 29, 2008 4:06 PMTo: talk@webdna.usSubject: Re: [WebDNA] SQLExecute Memory Leak=20Hello 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=20*All Platforms:=20*Fixed a memory leak with the database cache code. High volume sitewould be most affected by the memory leak, as it only occured when more =thanone thread required access to the same database at the same time.=20Thank you,Greg.At 03:53 PM 7/29/2008, you wrote:Hi,=20We have been using Webdna for a few years now. At least twice a day theDBServer.exe memory gets sky high. =13WebCatalog does not have enough =memoryto complete this command=14 is logged to the errorlog.txt, and the =serviceneeds to be restarted.=20=20We were able to narrow one of the issues to the SQLExecute statements =thatwe use. With every query made the memory climbs, and does not go down =oncethe query has been completed.=20=20Has anyone else found this to be an issue?=20We are using a Mysql Database (version 4.1.20). The Web server is =runningWindows 2003. We are using WebDNA version 6.1.=20Thanks!=20------=_NextPart_000_003A_01C8F1C4.6429BC80Content-Type: text/html;charset="us-ascii"Content-Transfer-Encoding: quoted-printable
But I am using a later version =(6.1). I assumethat the problem would have been resolved for this version. =
From: Greg =Kesler[mailto:gregk@clarityconnect.com]
Sent: Tuesday, July 29, =2008 4:06PM
To: talk@webdna.us
Subject: Re: [WebDNA] =SQLExecuteMemory Leak
Hello =Sarah:
I checked the revision list at:
http://webdna.smithmicro.com/ref/WebDNA%20Change%20Histo=ry.html
There 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 theDBServer.exe memory gets sky high. WebCatalog does not have enough =memoryto complete this command is logged to the errorlog.txt, and the =serviceneeds to be restarted.
We were able to narrow one of the issues to the SQLExecute statements =that weuse. With every query made the memory climbs, and does not go down once =thequery 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!
------=_NextPart_000_003A_01C8F1C4.6429BC80--
Associated Messages, from the most recent to the oldest:
This is a multi-part message in MIME format.------=_NextPart_000_003A_01C8F1C4.6429BC80Content-Type: text/plain;charset="us-ascii"Content-Transfer-Encoding: quoted-printableBut I am using a later version (6.1). I assume that the problem would =havebeen resolved for this version.=20=20 _____ =20From: Greg Kesler [mailto:gregk@clarityconnect.com]=20Sent: Tuesday, July 29, 2008 4:06 PMTo: talk@webdna.usSubject: Re: [WebDNA] SQLExecute Memory Leak=20Hello 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=20*All Platforms:=20*Fixed a memory leak with the database cache code. High volume sitewould be most affected by the memory leak, as it only occured when more =thanone thread required access to the same database at the same time.=20Thank you,Greg.At 03:53 PM 7/29/2008, you wrote:Hi,=20We have been using Webdna for a few years now. At least twice a day theDBServer.exe memory gets sky high. =13WebCatalog does not have enough =memoryto complete this command=14 is logged to the errorlog.txt, and the =serviceneeds to be restarted.=20=20We were able to narrow one of the issues to the SQLExecute statements =thatwe use. With every query made the memory climbs, and does not go down =oncethe query has been completed.=20=20Has anyone else found this to be an issue?=20We are using a Mysql Database (version 4.1.20). The Web server is =runningWindows 2003. We are using WebDNA version 6.1.=20Thanks!=20------=_NextPart_000_003A_01C8F1C4.6429BC80Content-Type: text/html;charset="us-ascii"Content-Transfer-Encoding: quoted-printable
But I am using a later version =(6.1). I assumethat the problem would have been resolved for this version. =
From: Greg =Kesler[mailto:gregk@clarityconnect.com]
Sent: Tuesday, July 29, =2008 4:06PM
To: talk@webdna.us
Subject: Re: [WebDNA] =SQLExecuteMemory Leak
Hello =Sarah:
I checked the revision list at:
http://webdna.smithmicro.com/ref/WebDNA%20Change%20Histo=ry.html
There 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 theDBServer.exe memory gets sky high. WebCatalog does not have enough =memoryto complete this command is logged to the errorlog.txt, and the =serviceneeds to be restarted.
We were able to narrow one of the issues to the SQLExecute statements =that weuse. With every query made the memory climbs, and does not go down once =thequery 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!
------=_NextPart_000_003A_01C8F1C4.6429BC80--
"Sarah Nussbaum"
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:
[WebDNA] Case-insensitive URLs (2011)
[CART] (1997)
Sorting by date (1997)
Online reference (1997)
Summary search -- speed (1997)
OPEN MARKET PATENTS SOUND ECOMMERCE ALARM (1998)
Webcatalog error, Plug-in for Webstar (1996)
Time Remaining? (1998)
Looking for 5 to 12 shops with 3 URLs & statements (1997)
Applescript error (1998)
WebCat2: Items xx to xx shown, etc. (1997)
EIMS Problems (1997)
breaking & sorting (2000)
OR in Showifs (Was: Secure Web Server) (1999)
WebCat2 several catalogs? (1997)
select multiple (1997)
weiered lookup (2004)
WebCatalog usage (1997)
question: webdelivery folder and file (1997)
FAX orders (1996)