On Mon, 2010-08-30 at 14:33 -0700, jhinckel wrote: > What I discovered were different in the logs several messages like: > > trigger seeding of SecureRandom > done seeding SecureRandom > keystore is: > KeyStore type is: jks > KeyStore provider is: > init keystore > init keymanager of type SunX509 > truststore is: E: \ Program Files \ Java \ jdk1.6.0_14 \ jre \ lib \ > security \ cacerts > truststore type is: jks > truststore provider is: > init truststore > adding the trusted cert: > Subject: CN = SwissSign Platinum CA - G2, O = SwissSign AG, C = CH > Issuer: CN = SwissSign Platinum CA - G2, O = SwissSign AG, C = CH > Algorithm: RSA; Serial number: 0x4eb200670c035d4f > Valid from Fri Oct 25 05:36:00 GMT-03: 00 2006 Until Sat Oct 25 05:36:00 > GMT-03: 00 2036 > > adding the trusted cert: > ... > adding the trusted cert: > ... > > preceding the passage which is common to both: > > trigger seeding of SecureRandom > done seeding SecureRandom > main, setSoTimeout (60000) called (after this line the system wait 5 > seconds) > %% No cached client session > *** ClientHello, TLSv1 >
I do not have any rational explanation for this (mis)behavior. You may want to try out different SSL context initialization strategies (for instance, by using older SSLv3 algorithm instead of TLSv2, pre-seeding SecureRandom, and so on) and see if that makes any difference. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
