Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Web Services / August 2005

Tip: Looking for answers? Try searching our database.

soap.tcp  - *very* slow

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Anna - 10 Aug 2005 06:45 GMT
Hi,
I'm using WSE 2.0 SP2; using soap.tcp as in TcpSyncStockService sample; my
soap service is used to retrieve/put in data from/to database.  The only
difference is I didn't include Main() in the Service project. The service is
started by the client the following way (please tell me if this design is
wrong, thanks):

EndpointReference endpoint = new EndpointReference(address, via);
if ( !SoapReceivers.Contains(endpoint) )
{
  SoapReceivers.Add( endpoint, typeof(MySoapService) );
  //Adding username token to global cache...
}
   
The communication is fine, the data are brought back correctly (well, most
of the time but this is another issue).  The main problem: it is
*unbelievably" slow.  It is significantly slower than when I had a standard
web service. I'm using the same server, the same database, same stored
procedures... And it is all still on localhost. While debugging I could
easily see how long it takes for the call to the server to get some data to
actually be executed - you can easily drink half cup of coffee in that time.  
From what I read I understood that communication over TCP should be faster
than HTTP, so it must be my mistake.  What is wrong with my design?  Any
guesses, hints, solutions and suggestions will be very much appreciated.

Anna
       
           
JohnnySparkles - 18 Aug 2005 03:23 GMT
Hi Anna,

Are you using X509 certificates for the security by any chance? I had a
similar problem that was caused because the URL's in the certificates I was
using weren't correct and had to wait for time-outs before the message could
be sent.

I think your code says it's using Username Token so you should check and see
if there are any url's inside that which may also need to be resolved.

You could also try running a  performance tool to see exactly where the time
is being spent.

Good Luck
Johnny

> Hi,
> I'm using WSE 2.0 SP2; using soap.tcp as in TcpSyncStockService sample; my
[quoted text clipped - 24 lines]
>        
>            

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.