[WebDNA] triggers executed at boot instead of scheduled time

This WebDNA talk-list message is from

2011

It keeps the original formatting. numero = 107173
interpreted = N
texte = This is a multi-part message in MIME format.--------------030707050906050608030708Content-Type: text/plain; charset=ISO-8859-1; format=flowedContent-Transfer-Encoding: 7bitHi,I had some strange corruption happen today. I lost the ability to tcp connect to both our credit card processor and UPS. I checked the resources on the server and it had tons of ram available and only a few of the 8 processors indicated a little more that 10% usage each.I rebooted the box and everything appeared to run ok except I discovered that the trigger to batch the days credit card business that is set to execute at 23:59:50 executed as soon as all the processes were up and running after the reboot. I further found fragments of tags placed in a few fields of the database that logs the credit card transactions.The server has (2) quad core 2.6 processors, 8GB of ram and 15K drives. Running WebDNA 6.2 on CentOS.Anyone have any ideas of what may cause something like this and will all triggers execute at boot regardless of their scheduled times?Thank you,Steve--------------030707050906050608030708Content-Type: text/html; charset=ISO-8859-1Content-Transfer-Encoding: 7bitHi,

I had some strange corruption happen today. I lost the ability to tcpconnect to both our credit card processor and UPS. I checked theresources on the server and it had tons of ram available and only a fewof the 8 processors indicated a little more that 10% usage each.

I rebooted the box and everything appeared to run ok except Idiscovered that the trigger to batch the days credit card business thatis set to execute at 23:59:50 executed as soon as all the processeswere up and running after the reboot. I further found fragments of tagsplaced in a few fields of the database that logs the credit cardtransactions.

The server has (2) quad core 2.6 processors, 8GB of ram and 15K drives.Running WebDNA 6.2 on CentOS.

Anyone have any ideas of what may cause something like this and willall triggers execute at boot regardless of their scheduled times?

Thank you,
Steve

--------------030707050906050608030708-- Associated Messages, from the most recent to the oldest:

Re: [WebDNA] triggers executed at boot instead of scheduled time ( 2011)
Re: [WebDNA] triggers executed at boot instead of scheduled time (Steve Raslevich - Northern Sound 2011)
Re: [WebDNA] triggers executed at boot instead of scheduled time (Donovan Brooke 2011)
[WebDNA] triggers executed at boot instead of scheduled time (Steve Raslevich - Northern Sound 2011)

This is a multi-part message in MIME format.--------------030707050906050608030708Content-Type: text/plain; charset=ISO-8859-1; format=flowedContent-Transfer-Encoding: 7bitHi,I had some strange corruption happen today. I lost the ability to tcp connect to both our credit card processor and UPS. I checked the resources on the server and it had tons of ram available and only a few of the 8 processors indicated a little more that 10% usage each.I rebooted the box and everything appeared to run ok except I discovered that the trigger to batch the days credit card business that is set to execute at 23:59:50 executed as soon as all the processes were up and running after the reboot. I further found fragments of tags placed in a few fields of the database that logs the credit card transactions.The server has (2) quad core 2.6 processors, 8GB of ram and 15K drives. Running WebDNA 6.2 on CentOS.Anyone have any ideas of what may cause something like this and will all triggers execute at boot regardless of their scheduled times?Thank you,Steve--------------030707050906050608030708Content-Type: text/html; charset=ISO-8859-1Content-Transfer-Encoding: 7bitHi,

I had some strange corruption happen today. I lost the ability to tcpconnect to both our credit card processor and UPS. I checked theresources on the server and it had tons of ram available and only a fewof the 8 processors indicated a little more that 10% usage each.

I rebooted the box and everything appeared to run ok except Idiscovered that the trigger to batch the days credit card business thatis set to execute at 23:59:50 executed as soon as all the processeswere up and running after the reboot. I further found fragments of tagsplaced in a few fields of the database that logs the credit cardtransactions.

The server has (2) quad core 2.6 processors, 8GB of ram and 15K drives.Running WebDNA 6.2 on CentOS.

Anyone have any ideas of what may cause something like this and willall triggers execute at boot regardless of their scheduled times?

Thank you,
Steve

--------------030707050906050608030708-- Steve Raslevich - Northern Sound

DOWNLOAD WEBDNA NOW!

[WebDNA] triggers executed at boot instead of scheduled time

2011

Top Articles:

Related Readings: