Re: Detecting/limiting connections in the developer edition ...
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 59918
interpreted = N
texte = How about using [shell] and a program like Curl to do your connects rather than webdna's internal mechanism? ----- Original Message ----- From: "Kenneth Grome"
To: "WebDNA Talk" Sent: Saturday, November 06, 2004 8:07 AM Subject: Detecting/limiting connections in the developer edition ... > I'm using webdna developer edition on a WinXP computer on my LAN, and > I need a way to determine how many connections are currently open at > any moment in time. > > Once I have this information I can use it in my webdna script to > prevent webdna from opening any new connections if the engine has > already reached its connection limit. No one is browsing manually so > I do not have to deal with incoming connections. I am in fact using > this computer to run a webdna script that performs a series of > OUTGOING tcpconnects -- and these are the connections I need to limit. > > I need to insure that the number of these connections does not go > beyond webdna's built-in connection limit, because every time this > happens it 'freezes' webdna and prevents any more connections until I > restart the entire server. Yes, that's right, I must restart the > entire server in order to make webdna useful again after it reaches > its connection limit and stops responding to new requests. > > Not only that, but when webdna stops serving when it reaches its > connection limit, I have to manually quit one or more processes > before I can get it working again. I cannot simply go to the START > menu and ask the computer to restart because it never works unless I > also click a button in a dialog box that pops up and waits for me to > confirm that I want to force quit some other process that apparently > conflicts with webdna when it stops serving new connections. > > It would be really nice if webdna did not throw the OS into a > condition that forces me to manually quit a process on the server > before the server will restart and become functional again. But I > can avoid this problem *if* webdna itself would report the current > number of connections. Because if it can do this, I can use the > connection number it reports to prevent any new connections when > webdna's limit has already been reached. > > So tell me, is there any way to determine the current number of > connections? Perhaps something like a [connections] tag that is > undocumented but that actually exists and can be used to tell me how > many connections are actually open at any given moment? > > Or does this capability simply not exist in the current version of webdna? > > I have already tried using [waitforfile] to slow down the number of > connections webdna will open, and it actually slows down the rate at > which new connections are opened to one every 15 seconds -- not the > default 30 seconds that is claimed in the docs, so the docs should be > changed to reflect this fact. Nevertheless this does NOT prevent too > many new connections from being opened, because previously opened > connections can still remain open ... so it does not resolve the > problem I described here. > > What would be really nice, and extremely useful in this situation, > would be for webdna's tcpconnect context to have a tag that reports > whether or not each connection has actually been closed. This would > allow us to track each connection and determine whether or not it is > still open at any instant in time. By counting the number of > connections that have been opened and also closed, we could prevent > too many new connections from being opened ... > > Or even better would be a way to force-close a connection after a > pre-determined amount of time, or before the next tcpconnect is > opened. This would allow us to control the flow of our webdna > scripts so that they would not try to open new connections unless > webdna had not already reached its connection limit. > > Any thoughts or comments on this topic are very much appreciated, > especially of you are offering a possible solution to the problem -- > other than a suggestion to "buy an upgrade" -- which is an obvious > solution that is unacceptable in this situation. > > Thanks. > > -- > > Sincerely, > Kenneth Grome > www.kengrome.com > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > Web Archive of this list is at: http://webdna.smithmicro.com/ > ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
How about using [shell] and a program like Curl to do your connects rather than webdna's internal mechanism? ----- Original Message ----- From: "Kenneth Grome" To: "WebDNA Talk" Sent: Saturday, November 06, 2004 8:07 AM Subject: Detecting/limiting connections in the developer edition ... > I'm using webdna developer edition on a WinXP computer on my LAN, and > I need a way to determine how many connections are currently open at > any moment in time. > > Once I have this information I can use it in my webdna script to > prevent webdna from opening any new connections if the engine has > already reached its connection limit. No one is browsing manually so > I do not have to deal with incoming connections. I am in fact using > this computer to run a webdna script that performs a series of > OUTGOING tcpconnects -- and these are the connections I need to limit. > > I need to insure that the number of these connections does not go > beyond webdna's built-in connection limit, because every time this > happens it 'freezes' webdna and prevents any more connections until I > restart the entire server. Yes, that's right, I must restart the > entire server in order to make webdna useful again after it reaches > its connection limit and stops responding to new requests. > > Not only that, but when webdna stops serving when it reaches its > connection limit, I have to manually quit one or more processes > before I can get it working again. I cannot simply go to the START > menu and ask the computer to restart because it never works unless I > also click a button in a dialog box that pops up and waits for me to > confirm that I want to force quit some other process that apparently > conflicts with webdna when it stops serving new connections. > > It would be really nice if webdna did not throw the OS into a > condition that forces me to manually quit a process on the server > before the server will restart and become functional again. But I > can avoid this problem *if* webdna itself would report the current > number of connections. Because if it can do this, I can use the > connection number it reports to prevent any new connections when > webdna's limit has already been reached. > > So tell me, is there any way to determine the current number of > connections? Perhaps something like a [connections] tag that is > undocumented but that actually exists and can be used to tell me how > many connections are actually open at any given moment? > > Or does this capability simply not exist in the current version of webdna? > > I have already tried using [waitforfile] to slow down the number of > connections webdna will open, and it actually slows down the rate at > which new connections are opened to one every 15 seconds -- not the > default 30 seconds that is claimed in the docs, so the docs should be > changed to reflect this fact. Nevertheless this does NOT prevent too > many new connections from being opened, because previously opened > connections can still remain open ... so it does not resolve the > problem I described here. > > What would be really nice, and extremely useful in this situation, > would be for webdna's tcpconnect context to have a tag that reports > whether or not each connection has actually been closed. This would > allow us to track each connection and determine whether or not it is > still open at any instant in time. By counting the number of > connections that have been opened and also closed, we could prevent > too many new connections from being opened ... > > Or even better would be a way to force-close a connection after a > pre-determined amount of time, or before the next tcpconnect is > opened. This would allow us to control the flow of our webdna > scripts so that they would not try to open new connections unless > webdna had not already reached its connection limit. > > Any thoughts or comments on this topic are very much appreciated, > especially of you are offering a possible solution to the problem -- > other than a suggestion to "buy an upgrade" -- which is an obvious > solution that is unacceptable in this situation. > > Thanks. > > -- > > Sincerely, > Kenneth Grome > www.kengrome.com > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > Web Archive of this list is at: http://webdna.smithmicro.com/ > ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
"Aaron Lynch"
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:
Databases going to sleep (1998)
This [search] worked before update to 4.5.1 (2003)
Simple way to create unique SKU (1997)
[thisurl] (2004)
Bugs still *not* fixed as promised ... (2000)
Re:quit command on NT (1997)
Re:2nd WebCatalog2 Feature Request (1996)
Remove WebDNA context (2001)
customizing the color of user's pages (1997)
Where's Cart Created ? (1997)
Progress !! WAS: Trouble with formula.db (1997)
WebCat2 - [format thousands] (1997)
Re1000001: Setting up shop (1997)
Help Wanted - Stowe, Vermont (1999)
Re[2]: Using [Include] Context (1999)
[WebDNA] FastCGI version confusion (2011)
WebCat2: multiple currency support (1997)
Share Bulletin Board? (1998)
Shipping by order total (2003)
Re:quit command on NT (1997)