C
cj2
I have a TCP/IP server that accepts incoming TCP/IP traffic creating a
new thread to answer each request. The thread then takes the info and
calls a web service. The results of the web service call are then then
returned to the TCP/IP requestor and the thread ends. This process
usually takes less than a second. Each thread increments a counter when
starting and decrements it when finishing so the counter can be read to
find out how many threads or concurrent conversations are taking place
at any given time.
The problem seem to start as the count starts climbing into the teens.
The TCP/IP requests are being answered but then the threads last for
even a couple minutes before ending reporting they were "Unable to
connect to the remote server". The web service records all requests it
gets and it acts like it never saw any of those requests.
So for some reason after we get a certain number of concurrent
conversations going on the calls to the web service are not able to
connect. Why? Any ideas?
new thread to answer each request. The thread then takes the info and
calls a web service. The results of the web service call are then then
returned to the TCP/IP requestor and the thread ends. This process
usually takes less than a second. Each thread increments a counter when
starting and decrements it when finishing so the counter can be read to
find out how many threads or concurrent conversations are taking place
at any given time.
The problem seem to start as the count starts climbing into the teens.
The TCP/IP requests are being answered but then the threads last for
even a couple minutes before ending reporting they were "Unable to
connect to the remote server". The web service records all requests it
gets and it acts like it never saw any of those requests.
So for some reason after we get a certain number of concurrent
conversations going on the calls to the web service are not able to
connect. Why? Any ideas?