JDK-8154910 : The specified module could not be found exception in test SupportedDHKeys
  • Type: Bug
  • Component: security-libs
  • Sub-Component: javax.crypto
  • Affected Version: 9
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2016-04-22
  • Updated: 2016-06-13
  • Resolved: 2016-06-13
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 9
9Resolved
Related Reports
Duplicate :  
JDK-8077138 - Some PKCS11 tests fail because NSS library is not initialized
Duplicate :  
JDK-8154406 - two sun/security/pkcs11/KeyAgreement/ tests failed with "java.security.ProviderException: Initialization failed" on Windows
Relates :  
JDK-8156991 - Problem list UnsupportedDHKeys.java on windows
Description

    Note: C:\jprt\T\P1\221154.vpeng\s\jdk\test\sun\security\pkcs11\PKCS11Test.java uses unchecked or unsafe operations.
    Note: Recompile with -Xlint:unchecked for details.

    ACTION: main -- Failed. Execution failed: `main' threw exception: java.security.ProviderException: Initialization failed
    REASON: User specified action: run main/othervm SupportedDHKeys 
    TIME:   0.281 seconds
    messages:
    command: main SupportedDHKeys
    reason: User specified action: run main/othervm SupportedDHKeys 
    elapsed time (seconds): 0.281
    STDOUT:
    libsoftokn3 version = 3.16.  ECC Extended.
    Beginning test run SupportedDHKeys...
    STDERR:
    java.security.ProviderException: Initialization failed
    	at sun.security.pkcs11.SunPKCS11.<init>(jdk.crypto.pkcs11@9-internal/SunPKCS11.java:380)
    	at sun.security.pkcs11.SunPKCS11$1.run(jdk.crypto.pkcs11@9-internal/SunPKCS11.java:111)
    	at sun.security.pkcs11.SunPKCS11$1.run(jdk.crypto.pkcs11@9-internal/SunPKCS11.java:108)
    	at java.security.AccessController.doPrivileged(java.base@9-internal/Native Method)
    	at sun.security.pkcs11.SunPKCS11.configure(jdk.crypto.pkcs11@9-internal/SunPKCS11.java:108)
    	at PKCS11Test.getSunPKCS11(PKCS11Test.java:151)
    	at PKCS11Test.testNSS(PKCS11Test.java:518)
    	at PKCS11Test.main(PKCS11Test.java:203)
    	at SupportedDHKeys.main(SupportedDHKeys.java:125)
    	at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@9-internal/Native Method)
    	at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@9-internal/NativeMethodAccessorImpl.java:62)
    	at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@9-internal/DelegatingMethodAccessorImpl.java:43)
    	at java.lang.reflect.Method.invoke(java.base@9-internal/Method.java:531)
    	at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:110)
    	at java.lang.Thread.run(java.base@9-internal/Thread.java:804)
    Caused by: java.io.IOException: The specified module could not be found.
    C:\jprt\T\P1\221154.vpeng\s\jdk\test\sun\security\pkcs11\nss\lib\windows-i586\softokn3.dll
    	at sun.security.pkcs11.wrapper.PKCS11.connect(jdk.crypto.pkcs11@9-internal/Native Method)
    	at sun.security.pkcs11.wrapper.PKCS11.<init>(jdk.crypto.pkcs11@9-internal/PKCS11.java:138)
    	at sun.security.pkcs11.wrapper.PKCS11.getInstance(jdk.crypto.pkcs11@9-internal/PKCS11.java:151)
    	at sun.security.pkcs11.SunPKCS11.<init>(jdk.crypto.pkcs11@9-internal/SunPKCS11.java:317)
    	... 14 more

    JavaTest Message: Test threw exception: java.security.ProviderException: Initialization failed
    JavaTest Message: shutting down test


 And same goes for the UnsupportedDHKeys test as well.

    Beginning test run UnsupportedDHKeys...
    STDERR:
    java.security.ProviderException: Initialization failed

BTW, -------------------------------------------
command: build SupportedDHParamGens
reason: Named class compiled on demand
elapsed time (seconds): 0.0

ACTION: main -- Error. Agent error: java.lang.Exception: Agent timed out
with a timeout of 1800 seconds; check console log for any additional
details
REASON: User specified action: run main/timeout=450 SupportedDHParamGens
3072


Also found this test failure in a JPRT run:
---------------------------------------------------
command: build SupportedDHParamGens
reason: Named class compiled on demand
elapsed time (seconds): 0.0

ACTION: main -- Error. Agent error: java.lang.Exception: Agent timed out
with a timeout of 1800 seconds; check console log for any additional
details
REASON: User specified action: run main/timeout=450 SupportedDHParamGens
3072
-------------------------------------------
Comments
Should this be closed as duplicate of JDK-8077138? We should add these tests to problemList for windows.
13-05-2016
These 2 tests fail pretty frequently on mach5 for windows-x86 (32/175 runs). http://java-dev.se.oracle.com/mach5//view/All/job/9-dev/374/artifact/failureHistory/tier2-windows-x64.html http://java-dev.se.oracle.com/mach5//view/All/job/9-dev/374/artifact/failureHistory/tier2-windows-x86.html
13-05-2016
Again I think it's because the DLL is not executable. You can see there are many many pkcs11 tests in the problem list. I just wonder why the tests fail on some platform and not on others.
22-04-2016