[WebDNA] autonumber duplication, time stamp issue & locking up

This WebDNA talk-list message is from

2010


It keeps the original formatting.
numero = 105440
interpreted = N
texte = This is a multi-part message in MIME format. --------------090408040103010601060500 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi all, First, I am rather a newbie to WebDNA so please bear with me. Up until today, I have been mostly using WebDNA for inter office admin stuff, sending out our monthly email newsletter (which from an earlier post I did resolve the sending duplicate email issue) but mostly for slowly creating a new website for my business. Nothing really demanding until today when we sent out 23K+ emails announcing a "register-to-win" contest and placed a link on our ancient html site to a WebDNA form page running on our Linux server. Within the first 3 1/2 hours after sending out the email, the form processed just short of 500 entries. #1) In this short time, the [autonumber] function created at least (2) identical, yet uniquely autonumbered records for (2) different customer submits. Both duplicate entries show a unique autonumber 1 apart from each other and show a time stamp of exactly the same time down to the second. The user clicking the submit button more than once should not be the issue here. I have the contest limited to one entrant per email address per month. When the form is submitted, it first searches the contest.db file for an existing record generated this month that contains the same email address being submitted. WebDNA should have found the first record and not written the second record due to the email address match but it did so twice. The time between the two occurrences is roughly 3 hours. #2) There are multiple instances in the contest database where records are logged out of time sequence compared to the autonumber. Example: record autonumbered 1138 has a time stamp (field) of 18:50:10 the following record autonumbered 1139 has a time stamp of 18:49:55, a few seconds earlier. Shouldn't the greater autonumber be written at a time after the lesser autonumber records time? When using [time], isn't WebDNA getting the time from the server that is also determining and writing the [autonumber]? #3) I have been going in regularly and searching the contest.db to see how many entries have been created. On occasion, the entire website seems to be locking up. No page will load. Not even the WebCatalog page. I don't get a time out error, it just sits there with the hour glass spinning and saying it's waiting for.... I had my local certified Linux specialist log in to our server and he claims the box is coasting both in processor use and RAM. He also checked the Apache logs and found no issues. Of course it wasn't locked up while he was logged in and I had him on the phone. I don't see it being our bandwidth as our connection to the internet is 25M up/down fiber and the form only has about 20 fields. It goes from lightning fast to a total lockup which seems to last for 60 seconds or more at a time. Should I be flushing the cache after every write from the contest form or something like that? Anyone have any ideas or suggestions? Thanks, Steve --------------090408040103010601060500 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi all,

First, I am rather a newbie to WebDNA so please bear with me. Up until today, I have been mostly using WebDNA for inter office admin stuff, sending out our monthly email newsletter (which from an earlier post I did resolve the sending duplicate email issue) but mostly for slowly creating a new website for my business. Nothing really demanding until today when we sent out 23K+ emails announcing a "register-to-win" contest and placed a link on our ancient html site to a WebDNA form page running on our Linux server.

Within the first 3 1/2 hours after sending out the email, the form processed just short of 500 entries.

#1) In this short time, the [autonumber] function created at least (2) identical, yet uniquely autonumbered records for (2) different customer submits. Both duplicate entries show a unique autonumber 1 apart from each other and show a time stamp of exactly the same time down to the second. The user clicking the submit button more than once should not be the issue here. I have the contest limited to one entrant per email address per month. When the form is submitted, it first searches the contest.db file for an existing record generated this month that contains the same email address being submitted. WebDNA should have found the first record and not written the second record due to the email address match but it did so twice. The time between the two occurrences is roughly 3 hours.

#2) There are multiple instances in the contest database where records are logged out of time sequence compared to the autonumber.
Example:
record autonumbered 1138 has a time stamp (field) of 18:50:10
the following record autonumbered  1139 has a time stamp of 18:49:55, a few seconds earlier.
Shouldn't the greater autonumber be written at a time after the lesser autonumber records time?  When using [time], isn't WebDNA getting the time from the server that is also determining and writing the [autonumber]?

#3) I have been going in regularly and searching the contest.db to see how many entries have been created. On occasion, the entire website seems to be locking up. No page will load. Not even the WebCatalog page. I don't get a time out error, it just sits there with the hour glass spinning and saying it's waiting for.... I had my local certified Linux specialist log in to our server and he claims the box is coasting both in processor use and RAM. He also checked the Apache logs and found no issues. Of course it wasn't locked up while he was logged in and I had him on the phone. I don't see it being our bandwidth as our connection to the internet is 25M up/down fiber and the form only has about 20 fields. It goes from lightning fast to a total lockup which seems to last for 60 seconds or more at a time. Should I be flushing the cache after every write from the contest form or something like that?


Anyone have any ideas or suggestions?

Thanks,
Steve --------------090408040103010601060500-- Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] autonumber duplication, time stamp issue & locking up (Tom Duke 2010)
  2. Re: [WebDNA] autonumber duplication, time stamp issue & locking up (Steve Raslevich 2010)
  3. Re: [WebDNA] autonumber duplication, time stamp issue & locking up (Steve Raslevich 2010)
  4. Re: [WebDNA] autonumber duplication, time stamp issue & ("Terry Wilson" 2010)
  5. Re: [WebDNA] autonumber duplication, time stamp issue & locking up (Govinda 2010)
  6. Re: [WebDNA] autonumber duplication, time stamp issue & locking up (Steve Raslevich 2010)
  7. Re: [WebDNA] autonumber duplication, time stamp issue & locking up (Steve Raslevich 2010)
  8. Re: [WebDNA] autonumber duplication, time stamp issue & locking up (Dale Therio 2010)
  9. Re: [WebDNA] autonumber duplication, time stamp issue & locking up (Govinda 2010)
  10. [WebDNA] autonumber duplication, time stamp issue & locking up (Steve Raslevich 2010)
This is a multi-part message in MIME format. --------------090408040103010601060500 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi all, First, I am rather a newbie to WebDNA so please bear with me. Up until today, I have been mostly using WebDNA for inter office admin stuff, sending out our monthly email newsletter (which from an earlier post I did resolve the sending duplicate email issue) but mostly for slowly creating a new website for my business. Nothing really demanding until today when we sent out 23K+ emails announcing a "register-to-win" contest and placed a link on our ancient html site to a WebDNA form page running on our Linux server. Within the first 3 1/2 hours after sending out the email, the form processed just short of 500 entries. #1) In this short time, the [autonumber] function created at least (2) identical, yet uniquely autonumbered records for (2) different customer submits. Both duplicate entries show a unique autonumber 1 apart from each other and show a time stamp of exactly the same time down to the second. The user clicking the submit button more than once should not be the issue here. I have the contest limited to one entrant per email address per month. When the form is submitted, it first searches the contest.db file for an existing record generated this month that contains the same email address being submitted. WebDNA should have found the first record and not written the second record due to the email address match but it did so twice. The time between the two occurrences is roughly 3 hours. #2) There are multiple instances in the contest database where records are logged out of time sequence compared to the autonumber. Example: record autonumbered 1138 has a time stamp (field) of 18:50:10 the following record autonumbered 1139 has a time stamp of 18:49:55, a few seconds earlier. Shouldn't the greater autonumber be written at a time after the lesser autonumber records time? When using [time], isn't WebDNA getting the time from the server that is also determining and writing the [autonumber]? #3) I have been going in regularly and searching the contest.db to see how many entries have been created. On occasion, the entire website seems to be locking up. No page will load. Not even the WebCatalog page. I don't get a time out error, it just sits there with the hour glass spinning and saying it's waiting for.... I had my local certified Linux specialist log in to our server and he claims the box is coasting both in processor use and RAM. He also checked the Apache logs and found no issues. Of course it wasn't locked up while he was logged in and I had him on the phone. I don't see it being our bandwidth as our connection to the internet is 25M up/down fiber and the form only has about 20 fields. It goes from lightning fast to a total lockup which seems to last for 60 seconds or more at a time. Should I be flushing the cache after every write from the contest form or something like that? Anyone have any ideas or suggestions? Thanks, Steve --------------090408040103010601060500 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi all,

First, I am rather a newbie to WebDNA so please bear with me. Up until today, I have been mostly using WebDNA for inter office admin stuff, sending out our monthly email newsletter (which from an earlier post I did resolve the sending duplicate email issue) but mostly for slowly creating a new website for my business. Nothing really demanding until today when we sent out 23K+ emails announcing a "register-to-win" contest and placed a link on our ancient html site to a WebDNA form page running on our Linux server.

Within the first 3 1/2 hours after sending out the email, the form processed just short of 500 entries.

#1) In this short time, the [autonumber] function created at least (2) identical, yet uniquely autonumbered records for (2) different customer submits. Both duplicate entries show a unique autonumber 1 apart from each other and show a time stamp of exactly the same time down to the second. The user clicking the submit button more than once should not be the issue here. I have the contest limited to one entrant per email address per month. When the form is submitted, it first searches the contest.db file for an existing record generated this month that contains the same email address being submitted. WebDNA should have found the first record and not written the second record due to the email address match but it did so twice. The time between the two occurrences is roughly 3 hours.

#2) There are multiple instances in the contest database where records are logged out of time sequence compared to the autonumber.
Example:
record autonumbered 1138 has a time stamp (field) of 18:50:10
the following record autonumbered  1139 has a time stamp of 18:49:55, a few seconds earlier.
Shouldn't the greater autonumber be written at a time after the lesser autonumber records time?  When using [time], isn't WebDNA getting the time from the server that is also determining and writing the [autonumber]?

#3) I have been going in regularly and searching the contest.db to see how many entries have been created. On occasion, the entire website seems to be locking up. No page will load. Not even the WebCatalog page. I don't get a time out error, it just sits there with the hour glass spinning and saying it's waiting for.... I had my local certified Linux specialist log in to our server and he claims the box is coasting both in processor use and RAM. He also checked the Apache logs and found no issues. Of course it wasn't locked up while he was logged in and I had him on the phone. I don't see it being our bandwidth as our connection to the internet is 25M up/down fiber and the form only has about 20 fields. It goes from lightning fast to a total lockup which seems to last for 60 seconds or more at a time. Should I be flushing the cache after every write from the contest form or something like that?


Anyone have any ideas or suggestions?

Thanks,
Steve --------------090408040103010601060500-- Steve Raslevich

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:

Summing fields (1997) WebCatalog for guestbook ? (1997) Sort Order on a page search (1997) CyberCash Transaction Cost (1999) [SHOWIF] (1997) OK to delete records while finding them? (2000) Assigning new CART number (1997) [WebDNA] Max files size (2011) America Online Issues (1998) WebCat2: multiple currency support (1997) Re[2]: Feature: TCPconnect via SSL (1999) Hiccup ***** (1998) Ampersands in database fields? (1998) Paymethod question (1999) Emailer and Lack of Code Commenting (1999) More on the email templates (1997) Strange intermittent WebDNA problems (2008) problem with dates, NT version (1997) errormessages.db (1997) Nested tags count question (1997)