-
Bug
-
Resolution: Fixed
-
P3
-
7, 8, 9
-
b08
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8338241 | 23.0.2 | Shivangi Gupta | P3 | Resolved | Fixed | b01 |
JDK-8338245 | 21.0.6-oracle | Shivangi Gupta | P3 | Resolved | Fixed | b01 |
JDK-8340204 | 21.0.6 | Sonia Zaldana Calles | P3 | Resolved | Fixed | b01 |
JDK-8338246 | 17.0.14-oracle | Shivangi Gupta | P3 | Resolved | Fixed | b01 |
JDK-8340778 | 17.0.14 | Goetz Lindenmaier | P3 | Resolved | Fixed | b01 |
JDK-8338247 | 11.0.26-oracle | Shivangi Gupta | P3 | Resolved | Fixed | b01 |
provs = Security.getProviders();
This will start adding/removing some of the system providers, in addition to the local providers. I don't understand this, and think this was not the intent.
Also, with the rewrite of the delayed provider selection and without an implementation of sigimpl, I don't think we'll ever be getting to the removeProvider code, it's always going to be failing the getInstance call.
In addition, this test is failing on windows-i586 with the server compiler only. See 6915983. Could be -sameVM issue.
windows_i586-product-c2-jdk_security1
TEST: java/security/Security/SynchronizedAccess.java
JDK under test: (C:\temp\jprt\T1\T\182757~1.SS1\TESTPR~1\WINDOW~1.0-P)
java version "1.7.0-2010-02-10-182757.ss145989.tl-pit-jtreg"
Java(TM) SE Runtime Environment (build 1.7.0-2010-02-10-182757.ss145989.tl-pit-j
treg-administrator_2010_02_10_11_28-b00)
Java HotSpot(TM) Server VM (build 17.0-b08, mixed mode)
ACTION: build -- Passed. Build successful
REASON: Named class compiled on demand
TIME: 0.468 seconds
messages:
command: build SynchronizedAccess
reason: Named class compiled on demand
elapsed time (seconds): 0.468
ACTION: compile -- Passed. Compilation successful
REASON: .class file out of date or does not exist
TIME: 0.437 seconds
messages:
command: compile C:\temp\jprt\T1\T\182757.ss145989\source\test\java\security\Sec
urity\SynchronizedAccess.java
reason: .class file out of date or does not exist
elapsed time (seconds): 0.437
ACTION: main -- Error. Error while cleaning up threads after test
REASON: Assumed action based on file name: run main SynchronizedAccess
TIME: 124.844 seconds
messages:
command: main SynchronizedAccess
reason: Assumed action based on file name: run main SynchronizedAccess
elapsed time (seconds): 124.844
STDOUT:
STDERR:
TEST RESULT: Error. Error while cleaning up threads after test
- backported by
-
JDK-8338241 Regtest java/security/Security/SynchronizedAccess.java is incorrect
-
- Resolved
-
-
JDK-8338245 Regtest java/security/Security/SynchronizedAccess.java is incorrect
-
- Resolved
-
-
JDK-8338246 Regtest java/security/Security/SynchronizedAccess.java is incorrect
-
- Resolved
-
-
JDK-8338247 Regtest java/security/Security/SynchronizedAccess.java is incorrect
-
- Resolved
-
-
JDK-8340204 Regtest java/security/Security/SynchronizedAccess.java is incorrect
-
- Resolved
-
-
JDK-8340778 Regtest java/security/Security/SynchronizedAccess.java is incorrect
-
- Resolved
-
- relates to
-
JDK-4162583 Provider api implementations are not synchronized properly
-
- Resolved
-
-
JDK-8163571 java/security/Security/SynchronizedAccess.java failed timeout
-
- Closed
-
- links to
-
Commit(master) openjdk/jdk17u-dev/9e8a1c0c
-
Commit(master) openjdk/jdk21u-dev/e11e0388
-
Commit(master) openjdk/jdk23u/ed24b9e6
-
Commit(master) openjdk/jdk/330e520c
-
Review(master) openjdk/jdk17u-dev/2909
-
Review(master) openjdk/jdk21u-dev/934
-
Review(master) openjdk/jdk23u/50
-
Review(master) openjdk/jdk/19480