Re: Performance differences between Java 8,, 11, 14 and 16

2021-05-11 Thread Peter Firmstone
你好先生范, 不客气, https://github.com/pfirmstone/JGDMS/blob/trunk/qa/src/org/apache/river/test/impl/mahalo/RandomStressTest.java https://github.com/pfirmstone/JGDMS/blob/trunk/qa/src/org/apache/river/test/impl/mahalo/RandomStressTest.td With the follow property set to reproduce: org.apache.river.test

Re: Performance differences between Java 8,, 11, 14 and 16

2021-05-11 Thread Xuelei Fan
Hi Peter, For further understanding, may I know more details about the test code? Thanks, Xuelei > On May 11, 2021, at 10:31 PM, Peter Firmstone > wrote: > > Just ran some performance stress tests to compare performance between Java 8 > and Java 14 with SecurityManager enabled and using TLS

Performance differences between Java 8,, 11, 14 and 16

2021-05-11 Thread Peter Firmstone
Just ran some performance stress tests to compare performance between Java 8 and Java 14 with SecurityManager enabled and using TLSv1.3 secure communications. On Java 8, AccessController.getStackAccessControlContext[native]() is 7,741ms of process CPU consumption. On Java 11, AccessControlle

Re: [11u] RFR: 8153005: Upgrade the default PKCS12 encryption/MAC algorithms

2021-05-11 Thread Hohensee, Paul
There’s an extra blank line inserted at the end of java.security. Otherwise lgtm. I’m fine with using KnownOIDs.java from tip. One might object that now it’s in a different location and must be kept sync’ed with tip, but I don’t agree because the backported version must be updated only when a t

Integrated: 8266225: jarsigner is using incorrect security property to show weakness of certs

2021-05-11 Thread Hai-May Chao
On Thu, 6 May 2021 16:49:33 GMT, Hai-May Chao wrote: > Please review the change to jarsigner so it uses certpath security property > in order to properly display the weakness of the certificate algorithms. This pull request has now been integrated. Changeset: 995e9560 Author:Hai-May Chao

Re: RFR: 8266225: jarsigner is using incorrect security property to show weakness of certs [v2]

2021-05-11 Thread Hai-May Chao
On Fri, 7 May 2021 14:10:14 GMT, Weijun Wang wrote: >> Hai-May Chao has updated the pull request incrementally with one additional >> commit since the last revision: >> >> Test with new java.security file > > Marked as reviewed by weijun (Reviewer). @wangweij @seanjmullan Thanks for the revi

Re: RFR: 8266225: jarsigner is using incorrect security property to show weakness of certs [v2]

2021-05-11 Thread Sean Mullan
On Thu, 6 May 2021 20:57:13 GMT, Hai-May Chao wrote: >> Please review the change to jarsigner so it uses certpath security property >> in order to properly display the weakness of the certificate algorithms. > > Hai-May Chao has updated the pull request incrementally with one additional > commi

Re: RFR: 8164804: sun/security/ssl/SSLSocketImpl/CloseSocket.java makes not reliable time assumption [v3]

2021-05-11 Thread Fernando Guallini
> test sun/security/ssl/SSLSocketImpl/CloseSocket.java verifies the behavior > when a server closes the socket connection during a handshake. The server was > waiting a fixed 100ms before closing it, but there was no guarantee that the > client started the handshake before or during that time fr

Re: RFR: 8164804: sun/security/ssl/SSLSocketImpl/CloseSocket.java makes not reliable time assumption [v3]

2021-05-11 Thread Fernando Guallini
On Mon, 10 May 2021 15:40:49 GMT, Rajan Halade wrote: >> OK > > Can you please add this as a comment in a test file for clientThread > variable? I am sure we will have (failed) try to convert it to CountDownLatch > in future. @rhalade sure comment included - PR: https://git.openj