my dog learned polymorphism*
The moose likes Web Services and the fly likes webservice Https connection Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "webservice Https connection" Watch "webservice Https connection" New topic
Author

webservice Https connection

kumaresan thiyagu
Greenhorn

Joined: Sep 01, 2009
Posts: 2
hi,

i can establish https connection throw rampart module with signature SOAP xml. But i am getting 15 seconds delay for every transaction.

i debug my SSL message, i assume - fist it takes TLSv1 Protocol connection wont establish [taken 14 sec] then try to connect SSLv2 Protocol.

with in one second entire transaction happened.

Question: How do i specify SSLv2 throw org.apache.axis2.client.ServiceClient [ Axis2 1.4.1 ]?

Note: i can achieve throw HttpsURLConnection, like SSLContext. But i required throw Axis2

Thanks,

FYR,

%% No cached client session
*** ClientHello, TLSv1
RandomCookie: GMT: 1234866231 bytes = { 168, 251, 241, 112, 19, 73, 203, 227, 186, 142, 30, 110, 13, 204, 0, 119, 1, 136, 241, 191, 220, 18, 95, 33, 71, 79, 162, 151 }
Session ID: {}
Cipher Suites: [SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_DES_CBC_SHA, SSL_DHE_RSA_WITH_DES_CBC_SHA, SSL_DHE_DSS_WITH_DES_CBC_SHA, SSL_RSA_EXPORT_WITH_RC4_40_MD5, SSL_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA]
Compression Methods: { 0 }
***
[write] MD5 and SHA1 hashes: len = 73
0000: 01 00 00 45 03 01 4A 9B 90 37 A8 FB F1 70 13 49 ...E..J..7...p.I
0010: CB E3 BA 8E 1E 6E 0D CC 00 77 01 88 F1 BF DC 12 .....n...w......
0020: 5F 21 47 4F A2 97 00 00 1E 00 04 00 05 00 2F 00 _!GO........../.
0030: 33 00 32 00 0A 00 16 00 13 00 09 00 15 00 12 00 3.2.............
0040: 03 00 08 00 14 00 11 01 00 .........
Main Thread, WRITE: TLSv1 Handshake, length = 73
[write] MD5 and SHA1 hashes: len = 98
0000: 01 03 01 00 39 00 00 00 20 00 00 04 01 00 80 00 ....9... .......
0010: 00 05 00 00 2F 00 00 33 00 00 32 00 00 0A 07 00 ..../..3..2.....
0020: C0 00 00 16 00 00 13 00 00 09 06 00 40 00 00 15 ............@...
0030: 00 00 12 00 00 03 02 00 80 00 00 08 00 00 14 00 ................
0040: 00 11 4A 9B 90 37 A8 FB F1 70 13 49 CB E3 BA 8E ..J..7...p.I....
0050: 1E 6E 0D CC 00 77 01 88 F1 BF DC 12 5F 21 47 4F .n...w......_!GO
0060: A2 97 ..
Main Thread, WRITE: SSLv2 client hello message, length = 98
Main Thread, READ: TLSv1 Handshake, length = 1489


Ulf Dittmer
Marshal

Joined: Mar 22, 2005
Posts: 41137
    
  45
If you're using Rampart, why are you even using HTTPS (instead of the XML Encryption that Rampart supports)?


Ping & DNS - my free Android networking tools app
kumaresan thiyagu
Greenhorn

Joined: Sep 01, 2009
Posts: 2
Ulf Dittmer wrote:If you're using Rampart, why are you even using HTTPS (instead of the XML Encryption that Rampart supports)?



Thanks for your replay,

My Server end point is "https://xxxxx/xxx", So that i am using HTTPS Connection, My actual doubt is given below

Questaion:

1. How to set "SSLv2" in axis2[1.4.1] rampart configuration.
2. Per transaction it takes 15 second, what are all the possible way to fine tune the performance.
3. SOAPHttpsURLConnection takes 1 sec per transaction, but difficult to do the XML Signature.

i think, i may rice lot of question.................., i appreciate your valuable reply
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: webservice Https connection
 
Similar Threads
handshake between sap xi & tomcat over https. no trusted certificate found
http://xml.apache.org/axis/ HttpErrorCode:401
javax.xml.ws.WebServiceException: Failed to access the WSDL
WARNING: Exception getting SSL Cert java.net.SocketException: Socket Closed
SSL error