S
Shoff
Hi there,
I hope someone can help me.
I have a client app. being used by about 50 users. When thy open the
app, it calls a webservice on a local server to check what items the
user can access, and returns a list for them to choose from.
To build the list, the web service calls other web services
asynchronously, and aslo starts another thread to call a SQL server
database and get a dataset.
Everything works fine with one machine, but after rolling it out to
all the users, I find that every now and again the users first get an
"Underlying connectin was closed" error. By restarting the
application again they go in fine.
Have done some tests with ACT which also reflects this with only a 66%
success rate on the web service.
I cannot see how I can change the process on the web server as it
needs to bring back that data, and although if I put everything
synchronously it either times out or takes unacceptably long to return
the data.
The network is a standard 100MB line, and the server is local, with
Gigs of memory, 4 processors the lot.
If anyone has any ideas, I would appreciate any help.
Thanks.
I hope someone can help me.
I have a client app. being used by about 50 users. When thy open the
app, it calls a webservice on a local server to check what items the
user can access, and returns a list for them to choose from.
To build the list, the web service calls other web services
asynchronously, and aslo starts another thread to call a SQL server
database and get a dataset.
Everything works fine with one machine, but after rolling it out to
all the users, I find that every now and again the users first get an
"Underlying connectin was closed" error. By restarting the
application again they go in fine.
Have done some tests with ACT which also reflects this with only a 66%
success rate on the web service.
I cannot see how I can change the process on the web server as it
needs to bring back that data, and although if I put everything
synchronously it either times out or takes unacceptably long to return
the data.
The network is a standard 100MB line, and the server is local, with
Gigs of memory, 4 processors the lot.
If anyone has any ideas, I would appreciate any help.
Thanks.