-
Bug
-
Resolution: Duplicate
-
P2
-
None
-
5.0u6
-
x86
-
windows_xp
Operating System: Windows XP
OS version: Version 5.1 (build 2600.xpap2.050301-1526: Service Pack 1)
Product Name: JRE
Product version: 1.5.0_06-b05
Hardware platform: Dell workstation, Intel Pentium 4 2.80 GHz w/ 1GB of RAM
Full problem description: A client program calling Ciper.init() [with Sun's JCE provider] will cause a long pause and CPU pegged at 100% level. E.g., it took 90-110 seconds for a jar size of 10 Mb. The conditions for this to occur: (1) the client code resides in a large jar file and (2) the jar file is signed. Customer have test the same against JRE 1.5.0_01 and the same problem does not exist. They tested that if the jar file is not signed then the problem also does not exist. They are forced to package the classes that call Cipher.init into a different, very small jar file, as a temporary work-around. But Customer would like NOT to separate the jar file, and would like to find out what is the root cause for this strange behavior.
OS version: Version 5.1 (build 2600.xpap2.050301-1526: Service Pack 1)
Product Name: JRE
Product version: 1.5.0_06-b05
Hardware platform: Dell workstation, Intel Pentium 4 2.80 GHz w/ 1GB of RAM
Full problem description: A client program calling Ciper.init() [with Sun's JCE provider] will cause a long pause and CPU pegged at 100% level. E.g., it took 90-110 seconds for a jar size of 10 Mb. The conditions for this to occur: (1) the client code resides in a large jar file and (2) the jar file is signed. Customer have test the same against JRE 1.5.0_01 and the same problem does not exist. They tested that if the jar file is not signed then the problem also does not exist. They are forced to package the classes that call Cipher.init into a different, very small jar file, as a temporary work-around. But Customer would like NOT to separate the jar file, and would like to find out what is the root cause for this strange behavior.
- duplicates
-
JDK-6354728 Verification of signed JAR files is very slow (performance reduction)
- Resolved