Hello,
Please review the updated test to verify "jdk.security.provider.preferred"
security property in all platform.
Bug: https://bugs.openjdk.java.net/browse/JDK-8150512
Webrev: http://cr.openjdk.java.net/~ssahoo/8150512/webrev.00/
These test were initially planned to run on Solaris
On 02/18/2016 03:10 AM, Weijun Wang wrote:
There is another compatibility issue which is more important:
Today, we tell users to load their own PKCS11 provider with
-providerClass sun.security.pkcs11.SunPKCS11 -providerArg some.cfg
and seems the new options should be
-provider SunPKCS11
A new version of this review has been released. SSLContextImpl now uses
the double-check idiom to do lazy initialization for the
StatusResponseManager, which should reduce lock overhead. Thanks to
Xuelei for pointing this out.
http://cr.openjdk.java.net/~jnimeh/reviews/8145854/webrev.03/
--
Looks fine to me.
Thanks,
Xuelei
On 2/26/2016 2:30 AM, Jamil Nimeh wrote:
> A new version of this review has been released. SSLContextImpl now uses
> the double-check idiom to do lazy initialization for the
> StatusResponseManager, which should reduce lock overhead. Thanks to
> Xuelei for point
Hi All,
I am working with a OS/2 running on Java 1.3 with JSSE. Recently we
implemented TLS and few times the the whole application hangs when 1 thread
calls createSocket call. The same code works most times
I tried looking for the sources of JSSE in 2002 and could not find one. Any
help in troub
