Re: [BULK] Re: [WebDNA] triggers.db "next execute" fails to update

This WebDNA talk-list message is from

2012

It keeps the original formatting. numero = 108352
interpreted = N
texte = Kenneth,I've had the same issues on all my WebCat 4.x, 5.x, and 6.0 servers over the years. The problems does not seem to happen on 6.2 for me.In my case, I had many triggers in a single Sandbox that would work fine for months and then one of them would stop updating. Or, even stranger, it would update to some time into the future. It never happen often enough to figure out a pattern.My solution was to simply delete the next trigger date and time. Save. Open the trigger record again and let it fill in the next execute time on it's own.I always suspected that it would only happen when WebDNA was close to, or exceeded, the available RAM, but that's such a hard thing to figure out.-MatthewOn 1/29/2012 6:53 PM, Kenneth Grome wrote:> Nope, just>> Sincerely,> Kenneth Grome>>>>> Typo in your "Validation Text" ?>>>> On 29/01/2012, at 4:29 PM, Kenneth Grome wrote:>>> 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>>> ------------------------------------------------------->>> -- This message is sent to you because you are>>> subscribed to the mailing list.>>> To unsubscribe, E-mail to:>>> archives: http://mail.webdna.us/list/talk@webdna.us>>> Bug Reporting: support@webdna.us>> --------------------------------------------------------->> This message is sent to you because you are subscribed to>> the mailing list.>> To unsubscribe, E-mail to:>> archives: http://mail.webdna.us/list/talk@webdna.us>> Bug Reporting: support@webdna.us> ---------------------------------------------------------> This message is sent to you because you are subscribed to> the mailing list.> To unsubscribe, E-mail to:> archives: http://mail.webdna.us/list/talk@webdna.us> Bug Reporting: support@webdna.us>>>> -- > Matthew A Perosi> Corporate Consultant> Mobile Marketing Expert> Senior Web Developer> SEO Analyst& Educator>> Psi Prime, Inc.> 323 Union Blvd.> Totowa, NJ 07512>> Service: 973.413.8211> Training: 973.413.8214> Fax: 973.413.8217>> http://www.perosi.com Associated Messages, from the most recent to the oldest:

Kenneth,I've had the same issues on all my WebCat 4.x, 5.x, and 6.0 servers over the years. The problems does not seem to happen on 6.2 for me.In my case, I had many triggers in a single Sandbox that would work fine for months and then one of them would stop updating. Or, even stranger, it would update to some time into the future. It never happen often enough to figure out a pattern.My solution was to simply delete the next trigger date and time. Save. Open the trigger record again and let it fill in the next execute time on it's own.I always suspected that it would only happen when WebDNA was close to, or exceeded, the available RAM, but that's such a hard thing to figure out.-MatthewOn 1/29/2012 6:53 PM, Kenneth Grome wrote:> Nope, just>> Sincerely,> Kenneth Grome>>>>> Typo in your "Validation Text" ?>>>> On 29/01/2012, at 4:29 PM, Kenneth Grome wrote:>>> 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>>> ------------------------------------------------------->>> -- This message is sent to you because you are>>> subscribed to the mailing list.>>> To unsubscribe, E-mail to:>>> archives: http://mail.webdna.us/list/talk@webdna.us>>> Bug Reporting: support@webdna.us>> --------------------------------------------------------->> This message is sent to you because you are subscribed to>> the mailing list.>> To unsubscribe, E-mail to:>> archives: http://mail.webdna.us/list/talk@webdna.us>> Bug Reporting: support@webdna.us> ---------------------------------------------------------> This message is sent to you because you are subscribed to> the mailing list.> To unsubscribe, E-mail to:> archives: http://mail.webdna.us/list/talk@webdna.us> Bug Reporting: support@webdna.us>>>> -- > Matthew A Perosi> Corporate Consultant> Mobile Marketing Expert> Senior Web Developer> SEO Analyst& Educator>> Psi Prime, Inc.> 323 Union Blvd.> Totowa, NJ 07512>> Service: 973.413.8211> Training: 973.413.8214> Fax: 973.413.8217>> http://www.perosi.com "Psi Prime Inc, Matthew A Perosi "

DOWNLOAD WEBDNA NOW!

Re: [BULK] Re: [WebDNA] triggers.db "next execute" fails to update

2012

Top Articles:

Related Readings: