- 
    Bug 
- 
    Resolution: Fixed
- 
     P3 P3
- 
    10
- 
        b20
                    It seems that MSCAPI related tests leave too many entries in keystore, thus may cause mscapi/keytool/keystore related tests runs very slow.
One example: sun/security/mscapi/AccessKeyStore.java
It normally should take less than 2 seconds, but at the box on which many runs have been done, it took 36 seconds. From the .jtr, there are too much keystore entries:
----------System.out:(3394/85623)----------
SunMSCAPI provider classname is sun.security.mscapi.SunMSCAPI
[0]
anything (1960) [key-entry]
...
-------------------------------------------------
[12215]
anything (576) [key-entry]
(while for the machine at which test just took less than 2 seconds to complete, the last key-entry is [49])
            
One example: sun/security/mscapi/AccessKeyStore.java
It normally should take less than 2 seconds, but at the box on which many runs have been done, it took 36 seconds. From the .jtr, there are too much keystore entries:
----------System.out:(3394/85623)----------
SunMSCAPI provider classname is sun.security.mscapi.SunMSCAPI
[0]
anything (1960) [key-entry]
...
-------------------------------------------------
[12215]
anything (576) [key-entry]
(while for the machine at which test just took less than 2 seconds to complete, the last key-entry is [49])
- relates to
- 
                    JDK-8185844 MSCAPI doesn't list aliases correctly -           
- Resolved
 
-