[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:
BUG?-.html extention not working. (2000)
Separate SSL Server (1997)
Getting total number of items ordered (1997)
Mine Headers for E-mail (1998)
reading a email (2000)
Whats wrong with this???? (2001)
Bug or syntax error on my part? (1997)
Request for page test (2003)
Server problem? (1998)
Database Strategy - more... (1998)
Searching Numbers (2004)
WebCatalog seems to choke on large (2meg) html files. (1998)
problems with 2 tags (1997)
no global [username] or [password] displayed ... (1997)
Help name our technology! (1997)
Database changes (1998)
WebCat2_Mac RETURNs in .db (1997)
taxrate - off by 1 cent (1997)
Dealer locator (1998)
Find one not all, code not working (2003)