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