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 / December 2004

Tip: Looking for answers? Try searching our database.

Secure calls to Java web service takes long time

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Magnus Johannesson - 10 Nov 2004 11:33 GMT
I've implemented the sample in Simon Guest's article "WS-Security
Interoperability Using WSE 2.0 and Sun JWSDP 1.4"
(http://msdn.microsoft.com/webservices/default.aspx?pull=/library/en-us/dnbd
a/html/interopsun.asp). I've put the client app and the web service on two
different machines. The client app is running on a Windows 2000 machine and
I've tested the web service both on a Windows 2000 machine and on a Linux
Red Hat 9 machine and gotten the same results.

The problem I have is that when I use signing and encryption, the calls to
the web service are taking a long time to complete. When I make a call
without any signing or encryption, it takes about 1 second to complete, but
when I sign and encrypt both the request and the response, it takes 15-20
seconds to complete. Anyone know why the secure calls are taking such a long
time? Our machines are not very fast, but still?

The certificates and keys used to perform this differ between the client and
the service. The client uses the Windows CurrentUser certificate store,
while the web service uses a JKS (Java Key Store). The certificates and keys
used are the one ones supplied with WSE and JWSDP, respectively.

TIA,
Magnus
Dan Rogers - 03 Dec 2004 02:48 GMT
Hi Magnus,

I think you will need to figure out which part is slow - the client code,
or the server code.  If you are seeing the same behavior on a Linux client
and on a Microsoft ASP.NET client, then I'm going to guess that the Sun
code on the actual service is the bottleneck.

From there I really can't offer any direction other then go ask Sun!

Best regards

Dan Rogers
Microsoft Corporation
--------------------
From: "Magnus Johannesson" <magnus.johannesson@discussions.microsoft.com>
Subject: Secure calls to Java web service takes long time
Date: Wed, 10 Nov 2004 12:33:25 +0100
Lines: 24
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Message-ID: <egQGZkxxEHA.1192@tk2msftngp13.phx.gbl>
Newsgroups: microsoft.public.dotnet.framework.webservices.enhancements
NNTP-Posting-Host: 212.91.131.144
Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13
.phx.gbl
Xref: cpmsftngxa10.phx.gbl
microsoft.public.dotnet.framework.webservices.enhancements:4812
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices.enhancements

I've implemented the sample in Simon Guest's article "WS-Security
Interoperability Using WSE 2.0 and Sun JWSDP 1.4"
(http://msdn.microsoft.com/webservices/default.aspx?pull=/library/en-us/dnbd
a/html/interopsun.asp). I've put the client app and the web service on two
different machines. The client app is running on a Windows 2000 machine and
I've tested the web service both on a Windows 2000 machine and on a Linux
Red Hat 9 machine and gotten the same results.

The problem I have is that when I use signing and encryption, the calls to
the web service are taking a long time to complete. When I make a call
without any signing or encryption, it takes about 1 second to complete, but
when I sign and encrypt both the request and the response, it takes 15-20
seconds to complete. Anyone know why the secure calls are taking such a long
time? Our machines are not very fast, but still?

The certificates and keys used to perform this differ between the client and
the service. The client uses the Windows CurrentUser certificate store,
while the web service uses a JKS (Java Key Store). The certificates and keys
used are the one ones supplied with WSE and JWSDP, respectively.

TIA,
Magnus

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.