Details
-
Bug
-
Resolution: Cannot Reproduce
-
P3
-
None
-
None
-
None
Description
A deadlock condition may occur when a main thread is attempting to verify a Jar signature and another thread, that might be started by certain JVM tools, has locked LocaleDataMetaInfo by using ServiceLoader and also expects to lock JarFile, which the main thread is already holding
The following test reproduces the main thread conditions:
java/security/Policy/SignedJar/SignedJarTest.java
sun/security/tools/jarsigner/multiRelease/MVJarSigningTest.java
The following test reproduces the main thread conditions:
java/security/Policy/SignedJar/SignedJarTest.java
sun/security/tools/jarsigner/multiRelease/MVJarSigningTest.java
Attachments
Issue Links
- duplicates
-
JDK-8266384 sun/security/tools/jarsigner/multiRelease/MVJarSigningTest.java timed out
- Resolved
-
JDK-8261915 3 strange security test failures
- Resolved
- relates to
-
JDK-8261915 3 strange security test failures
- Resolved
-
JDK-8269039 Disable SHA-1 Signed JARs
- Resolved