Retries or Give up at first attempt..
-
Most applications I work on seem to have a 'retry' count for connecting to various servers, especially database. They will, for example, retry up to 5 times, at 30 second intervals. I don't think in all my time I have seen an error log, warning, or eventlog entry where the connection failed on the 1st\2nd\3rd attempt etc, but connected successfully on a subsequent attempt. Years ago, networks were flakey, and a retry was deemed necessary incase of a network glitch - networks don't seem to 'glitch' anymore. Do you still code 'retries' in your apps, or give up at first attempt? OT : The 'click here to edit' bubble, hovering over the signature is kinda neat!
Knowledge is hereditary, it will find its way up or down. Luc Pattyn
and since what every time when i want to add button to this control one add two times posted in C# forum -
Most applications I work on seem to have a 'retry' count for connecting to various servers, especially database. They will, for example, retry up to 5 times, at 30 second intervals. I don't think in all my time I have seen an error log, warning, or eventlog entry where the connection failed on the 1st\2nd\3rd attempt etc, but connected successfully on a subsequent attempt. Years ago, networks were flakey, and a retry was deemed necessary incase of a network glitch - networks don't seem to 'glitch' anymore. Do you still code 'retries' in your apps, or give up at first attempt? OT : The 'click here to edit' bubble, hovering over the signature is kinda neat!
Knowledge is hereditary, it will find its way up or down. Luc Pattyn
and since what every time when i want to add button to this control one add two times posted in C# forumMalcolm Smart wrote:
Do you still code 'retries' in your apps, or give up at first attempt?
It depends. Windows Services, I guess, have Three attempts to deal with startup failure with a time interval and then notify administrator.
Vasudevan Deepak Kumar Personal Homepage
Tech Gossips
A pessimist sees only the dark side of the clouds, and mopes; a philosopher sees both sides, and shrugs; an optimist doesn't see the clouds at all - he's walking on them. --Leonard Louis Levinson -
Most applications I work on seem to have a 'retry' count for connecting to various servers, especially database. They will, for example, retry up to 5 times, at 30 second intervals. I don't think in all my time I have seen an error log, warning, or eventlog entry where the connection failed on the 1st\2nd\3rd attempt etc, but connected successfully on a subsequent attempt. Years ago, networks were flakey, and a retry was deemed necessary incase of a network glitch - networks don't seem to 'glitch' anymore. Do you still code 'retries' in your apps, or give up at first attempt? OT : The 'click here to edit' bubble, hovering over the signature is kinda neat!
Knowledge is hereditary, it will find its way up or down. Luc Pattyn
and since what every time when i want to add button to this control one add two times posted in C# forumI've done both but to be honest I think these days if it doesn't work there's likely to be something wrong. One of the things that used to cause the retry to work on a system I worked on in the late 90s was that the first try fired up the modem if the PC was remote. By the time the second attempt fired, the network connection was up and running. The exception for me would be something like bittorrent, skype or msn, where you want to be continually connected. If my app received a dropped connection error I might try an immediate connect and then one 30 secs later in case there was a hardware reboot etc going on. Russell
-
Most applications I work on seem to have a 'retry' count for connecting to various servers, especially database. They will, for example, retry up to 5 times, at 30 second intervals. I don't think in all my time I have seen an error log, warning, or eventlog entry where the connection failed on the 1st\2nd\3rd attempt etc, but connected successfully on a subsequent attempt. Years ago, networks were flakey, and a retry was deemed necessary incase of a network glitch - networks don't seem to 'glitch' anymore. Do you still code 'retries' in your apps, or give up at first attempt? OT : The 'click here to edit' bubble, hovering over the signature is kinda neat!
Knowledge is hereditary, it will find its way up or down. Luc Pattyn
and since what every time when i want to add button to this control one add two times posted in C# forumOutlook 03 would spam unable to reach exchange server click here to retry messages for about 15m after a reboot before connecting. outlook 07 just keeps silently retrying until the bogons leak out of the network cable.
Otherwise [Microsoft is] toast in the long term no matter how much money they've got. They would be already if the Linux community didn't have it's head so firmly up it's own command line buffer that it looks like taking 15 years to find the desktop. -- Matthew Faithfull
-
Most applications I work on seem to have a 'retry' count for connecting to various servers, especially database. They will, for example, retry up to 5 times, at 30 second intervals. I don't think in all my time I have seen an error log, warning, or eventlog entry where the connection failed on the 1st\2nd\3rd attempt etc, but connected successfully on a subsequent attempt. Years ago, networks were flakey, and a retry was deemed necessary incase of a network glitch - networks don't seem to 'glitch' anymore. Do you still code 'retries' in your apps, or give up at first attempt? OT : The 'click here to edit' bubble, hovering over the signature is kinda neat!
Knowledge is hereditary, it will find its way up or down. Luc Pattyn
and since what every time when i want to add button to this control one add two times posted in C# forumAn FTP app that I wrote connects to one server that invariably resets the connection in the middle of transmission. I catch the exception, destroy the connection and start over from the beginning again. It's in an endless loop condition, but the worst I've encountered is two resets. So it does still happen, but maybe so infrequent that most people don't bother with it.
Chris Meech I am Canadian. [heard in a local bar] Donate to help Conquer Cancer[^]
-
Most applications I work on seem to have a 'retry' count for connecting to various servers, especially database. They will, for example, retry up to 5 times, at 30 second intervals. I don't think in all my time I have seen an error log, warning, or eventlog entry where the connection failed on the 1st\2nd\3rd attempt etc, but connected successfully on a subsequent attempt. Years ago, networks were flakey, and a retry was deemed necessary incase of a network glitch - networks don't seem to 'glitch' anymore. Do you still code 'retries' in your apps, or give up at first attempt? OT : The 'click here to edit' bubble, hovering over the signature is kinda neat!
Knowledge is hereditary, it will find its way up or down. Luc Pattyn
and since what every time when i want to add button to this control one add two times posted in C# forumA subtle bug that almost drove me insane in 2006 was due to the DB server being rebooted weekly. The app would start losing connections, but since there was a pool of them, it would still function. After 3 or 4 days, it would go down. I fixed it by re-establishing the connection after a few minutes, and was given an award. :-O
Cheers, Vikram.
Zeppelin's law: In any Soapbox discussion involving Stan Shannon, the probability of the term "leftist" or "Marxist" appearing approaches 1 monotonically. Harris' addendum: I think you meant "monotonously". Martin's second addendum: Jeffersonian... I think that should at least get a mention.
-
Most applications I work on seem to have a 'retry' count for connecting to various servers, especially database. They will, for example, retry up to 5 times, at 30 second intervals. I don't think in all my time I have seen an error log, warning, or eventlog entry where the connection failed on the 1st\2nd\3rd attempt etc, but connected successfully on a subsequent attempt. Years ago, networks were flakey, and a retry was deemed necessary incase of a network glitch - networks don't seem to 'glitch' anymore. Do you still code 'retries' in your apps, or give up at first attempt? OT : The 'click here to edit' bubble, hovering over the signature is kinda neat!
Knowledge is hereditary, it will find its way up or down. Luc Pattyn
and since what every time when i want to add button to this control one add two times posted in C# forumA subtle bug that almost drove me insane in 2006 was due to the DB server being rebooted weekly. The app would start losing connections, but since there was a pool of them, it would still function. After 3 or 4 days, it would go down. I fixed it by re-establishing the connection after a few minutes, and was given an award. :-O
Cheers, Vikram.
Zeppelin's law: In any Soapbox discussion involving Stan Shannon, the probability of the term "leftist" or "Marxist" appearing approaches 1 monotonically. Harris' addendum: I think you meant "monotonously". Martin's second addendum: Jeffersonian... I think that should at least get a mention.
-
A subtle bug that almost drove me insane in 2006 was due to the DB server being rebooted weekly. The app would start losing connections, but since there was a pool of them, it would still function. After 3 or 4 days, it would go down. I fixed it by re-establishing the connection after a few minutes, and was given an award. :-O
Cheers, Vikram.
Zeppelin's law: In any Soapbox discussion involving Stan Shannon, the probability of the term "leftist" or "Marxist" appearing approaches 1 monotonically. Harris' addendum: I think you meant "monotonously". Martin's second addendum: Jeffersonian... I think that should at least get a mention.
Vikram A Punathambekar wrote:
and was given an award
and you are so pleased with yourself you thought you'd post the message twice!
Knowledge is hereditary, it will find its way up or down. Luc Pattyn
and since what every time when i want to add button to this control one add two times posted in C# forum -
Vikram A Punathambekar wrote:
and was given an award
and you are so pleased with yourself you thought you'd post the message twice!
Knowledge is hereditary, it will find its way up or down. Luc Pattyn
and since what every time when i want to add button to this control one add two times posted in C# forum:laugh:
Cheers, Vikram.
Zeppelin's law: In any Soapbox discussion involving Stan Shannon, the probability of the term "leftist" or "Marxist" appearing approaches 1 monotonically. Harris' addendum: I think you meant "monotonously". Martin's second addendum: Jeffersonian... I think that should at least get a mention.
-
Vikram A Punathambekar wrote:
and was given an award
and you are so pleased with yourself you thought you'd post the message twice!
Knowledge is hereditary, it will find its way up or down. Luc Pattyn
and since what every time when i want to add button to this control one add two times posted in C# forumI don't think it is user-driven multiple post. I have observed it while posting the other day in Lounge. After submitting, the same post appeared twice. I had to compare manually the messageids shown in the permalink of each manually and delete the latter. Since there were no edits in the textbox after submit button was clicked, I really wonder, how did the 'Post Duplicate Detector' failed to notice this. I have actually logged the issue over here: http://www.codeproject.com/script/Forums/View.aspx?fid=1645&msg=2448993[^] Today I have also updated the issue with this observation also. I think, CP Team should be able to help out with a resolution. But this is kind of random bug and not reproducible consistently.
Vasudevan Deepak Kumar Personal Homepage
Tech Gossips
A pessimist sees only the dark side of the clouds, and mopes; a philosopher sees both sides, and shrugs; an optimist doesn't see the clouds at all - he's walking on them. --Leonard Louis Levinson -
:laugh:
Cheers, Vikram.
Zeppelin's law: In any Soapbox discussion involving Stan Shannon, the probability of the term "leftist" or "Marxist" appearing approaches 1 monotonically. Harris' addendum: I think you meant "monotonously". Martin's second addendum: Jeffersonian... I think that should at least get a mention.
Vikram A Punathambekar wrote:
irony
And half-credit also goes to a bug in 'Posting Duplicate Detector': http://www.codeproject.com/script/Forums/View.aspx?fid=1159&msg=2452934[^] :)
Vasudevan Deepak Kumar Personal Homepage
Tech Gossips
A pessimist sees only the dark side of the clouds, and mopes; a philosopher sees both sides, and shrugs; an optimist doesn't see the clouds at all - he's walking on them. --Leonard Louis Levinson -
Most applications I work on seem to have a 'retry' count for connecting to various servers, especially database. They will, for example, retry up to 5 times, at 30 second intervals. I don't think in all my time I have seen an error log, warning, or eventlog entry where the connection failed on the 1st\2nd\3rd attempt etc, but connected successfully on a subsequent attempt. Years ago, networks were flakey, and a retry was deemed necessary incase of a network glitch - networks don't seem to 'glitch' anymore. Do you still code 'retries' in your apps, or give up at first attempt? OT : The 'click here to edit' bubble, hovering over the signature is kinda neat!
Knowledge is hereditary, it will find its way up or down. Luc Pattyn
and since what every time when i want to add button to this control one add two times posted in C# forumThey are usually load bearing from some other flaw. Ie, it won't connect the first time but should connect the second. Lazy developers never think that there could be a flaw in their code and such things persist.
Need a C# Consultant? I'm available.
Happiness in intelligent people is the rarest thing I know. -- Ernest Hemingway -
Most applications I work on seem to have a 'retry' count for connecting to various servers, especially database. They will, for example, retry up to 5 times, at 30 second intervals. I don't think in all my time I have seen an error log, warning, or eventlog entry where the connection failed on the 1st\2nd\3rd attempt etc, but connected successfully on a subsequent attempt. Years ago, networks were flakey, and a retry was deemed necessary incase of a network glitch - networks don't seem to 'glitch' anymore. Do you still code 'retries' in your apps, or give up at first attempt? OT : The 'click here to edit' bubble, hovering over the signature is kinda neat!
Knowledge is hereditary, it will find its way up or down. Luc Pattyn
and since what every time when i want to add button to this control one add two times posted in C# forumIt's a good idea to have if the connection dies during a session. Perhaps the DB admin rebooted the server or something. The retry logic can attemp to reconnect the user without them having to do a manual retry, retry, retry, retry...
Todd Smith
-
Most applications I work on seem to have a 'retry' count for connecting to various servers, especially database. They will, for example, retry up to 5 times, at 30 second intervals. I don't think in all my time I have seen an error log, warning, or eventlog entry where the connection failed on the 1st\2nd\3rd attempt etc, but connected successfully on a subsequent attempt. Years ago, networks were flakey, and a retry was deemed necessary incase of a network glitch - networks don't seem to 'glitch' anymore. Do you still code 'retries' in your apps, or give up at first attempt? OT : The 'click here to edit' bubble, hovering over the signature is kinda neat!
Knowledge is hereditary, it will find its way up or down. Luc Pattyn
and since what every time when i want to add button to this control one add two times posted in C# forumMalcolm Smart wrote:
OT : The 'click here to edit' bubble, hovering over the signature is kinda neat!
Sure, but how many times do you need to retry?