[WebDNA] triggers.db "next execute" fails to update
This WebDNA talk-list message is from 2012
It keeps the original formatting.
numero = 108336
interpreted = N
texte = I created a trigger on WebDNA 6.x via WebDNA Sandbox Admin. This is the only trigger used in this sandbox. When it runs WebDNA fails update the "next execute" value like it is supposed to. Therefore the trigger runs again every 10 seconds, and the same template is interpreted by WebDNA again ... This is a "bad thing" when the template has a sendmail context it it to alert me that the trigger has run, because it sends me another email every 10 seconds. I got more than 1500 emails this morning before the host put an end to it by rebooting the server ... :( Flushing the databases does not stop the trigger from running. Deleting the target template via FTP does not stop it, because even though the file is no longer on disk it is apparently still cached in RAM. Strangely enough, the template seems to remain cached in RAM , thus ignoring the WebCatalog Prefs that's supposed to force the template out of ram every 2 seconds. Issuing a FlushCache command also fails to purge the template from RAM. :( My host refuses to investigate this issue. Whether he is lazy, irresponsible, incompetent, or all of the above, cannot say for certain. Nevertheless I need the problem fixed, so I'll have to figure this out myself, hopefully with some bright ideas from others here. Any idea why WebDNA might fail to update the "next execute" value when the trigger is run? Sincerely, Kenneth Grome
Associated Messages, from the most recent to the oldest:
I created a trigger on WebDNA 6.x via WebDNA Sandbox Admin. This is the only trigger used in this sandbox. When it runs WebDNA fails update the "next execute" value like it is supposed to. Therefore the trigger runs again every 10 seconds, and the same template is interpreted by WebDNA again ... This is a "bad thing" when the template has a sendmail context it it to alert me that the trigger has run, because it sends me another email every 10 seconds. I got more than 1500 emails this morning before the host put an end to it by rebooting the server ... :( Flushing the databases does not stop the trigger from running. Deleting the target template via FTP does not stop it, because even though the file is no longer on disk it is apparently still cached in RAM. Strangely enough, the template seems to remain cached in RAM , thus ignoring the WebCatalog Prefs that's supposed to force the template out of ram every 2 seconds. Issuing a FlushCache command also fails to purge the template from RAM. :( My host refuses to investigate this issue. Whether he is lazy, irresponsible, incompetent, or all of the above, cannot say for certain. Nevertheless I need the problem fixed, so I'll have to figure this out myself, hopefully with some bright ideas from others here. Any idea why WebDNA might fail to update the "next execute" value when the trigger is run? Sincerely, Kenneth Grome
Kenneth Grome
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:
Sami (1998)
Protect vs Authenicate (1997)
OSX Applescripts -- Anyone? please? (2004)
DON'T use old cart file! (1997)
Running 2 two WebCatalog.acgi's (1996)
listfiles-looking for slick solution (1997)
Template cache problem with WC4 on Mac OS X (2000)
Shopping Cart Problem (1998)
Text vs. Math (2000)
Case sensitivity and [showif] (1999)
Here's how to kill a Butler Database. (1997)
[date] BUG! (2002)
Location of Webcat site in folder hierarchy (1997)
File Upload (1997)
Missing Cart Information (2003)
date (2002)
WebCatalog Hosting (1996)
My solution... (1996)
WebCat2: Master Counter snippet (1997)
my price won't move (1997)