Groups | Blog | Home
all groups > dotnet web services enhancements > october 2005 >

dotnet web services enhancements : Huge delay when calling a method using a Wse proxy - Wse 3.0 Beta1


Zoodor
10/25/2005 9:09:05 AM
I have a web service that uses Wse.

My policy simply uses two (built-in) extensions:
The "usernameOverTransportSecurity" and the "requireActionHeader".

It works, but the problem is it takes ages for any web method to return. I
have an identical web service that is not wse-enabled and the non-wse call
takes milliseconds, whereas the wse one takes several seconds. The aspx page
(that calls the service) is on the same machine as the webservice. It is a
Windows 2003 machine. Running the aspx code on my development machine (WinXP
pro) connecting to the same web service has the exact same problem.

I have logged the time on the client just before and after the method call,
and on the server at the start and end of the method. It appears that there
is a 2-3 second delay between the client call on the proxy method and the
method on the server being called, and also between the method on the server
completing and the method on the proxy class returning.

Any ideas on what could be causing this massive performance problem and how
I could fix it? As you can imaging, it makes the web site unusably slow.

I am going to try using the October CTP of WSE and see if that makes a
difference, but I don't hold out much hope...

Zoodor
10/26/2005 12:20:06 AM
That sorted it, thank you!

I knew it would end up being something silly I'd done.

[quoted text, click to view]
Jon
10/26/2005 8:41:35 AM
If you have diagnostics enabled turn it off.
As those output files get larger the slower it goes.

[quoted text, click to view]

AddThis Social Bookmark Button