active connections on the G Web Server

[pwalsh]

Hello,

I'm using LV 7.1 with the G Web server in the development system.  Every now and then the active connections start growing and the server stops serving. 

I've surfed through the postings and have found similar problems.  One person mentioned that the cgi vi's have to be enclosed in while loops - which I have done. And it doesn't sound like re-entrant vi's fix the problem either. 

My vi's are all based upon the examples provided in the toolkit. Is there a way to re-program the Gweb server to terminate active connections when they start growing? Any workaround suggestions would be appreciated. 

Pat

[sarahk]

Hi, Pat.

I don't know of a way to re-program the server, but let me ask you a few questions about this:

- Does the server stop serving at the same number of connections each time?
- Do the connections start piling up when a particular VI is requested, or is it a different VI every time?

Let me know what happens. I think we'll be able to get things up and running again.

[pwalsh]

Sarah,

Thanks for the reply.

It appears to stop when the number of connections goes above 3.  And I've seen it happen with two different vi's. 

I actually just wrote a program that makes http requests continuously.  It calls one of the cgi vi's over and over.  I ran it from a couple of computers simultaneously.  My goal is overwhelm the server with requests.  Well it didn't work, and the server ran fine.   I'm pretty confused. When I find the a set of conditions that always lock up the server, I'll respond back.

Pat

[pwalsh]

Sarah, My problem was solved by moving the server to a better computer (2gig ram and 2.8gig pentium).  I have not seen it happen since.

Thanks

Pat

[sarahk]

Hi, Pat.

Thanks for letting me know. That's certainly strange behavior -- and I'm sorry we d=coulodn't determine the cause -- but I'm glad you're up and running again.

Have a nice afternoon!

[aartjan]

I am afraid it is not strange behaviour at all: I have been dealing with it for years. I never found the culprit, other than the outdated server engine used. I solved it somewhat by restarting the server automatically when going over 3 simultaneous connections. I also moved to a faser computer, which also lessened te problem.
To go short: it is a very well known bug, that NI has been ignoring, even through the the toolkit upgrade from 5 to 6.
Too bad...