JRE crashes after update to 26, if java.security file was changed.

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: P3
    • None
    • Affects Version/s: 6u26
    • Component/s: install
    • x86
    • windows_xp

      FULL PRODUCT VERSION :
      Before JRE crashes:

      java version "1.6.0_24"
      Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
      Java HotSpot(TM) Client VM (build 19.1-b02, mixed mode, sharing)

      ADDITIONAL OS VERSION INFORMATION :
      Microsoft Windows XP [ 5.1.2600]

      A DESCRIPTION OF THE PROBLEM :
      1. add "security.provider.10=com.test.Provider" to java.security file
      2. run update
      3. update shows the warning "lib\security\java.security: Old File not found...." and after finish JRE can't work. If we run java.exe the following dialog appear:
      "The procedure entry point _JVM_LoadSystemLibrary@4 could not be located in dynamic link library jvm.dll"

      REGRESSION. Last worked in version 6u26

      STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
      1. add "security.provider.10=com.test.Provider" to java.security file
      2. run update
      3. update shows the warning "lib\security\java.security: Old File not found...." and after finish JRE can't work. If we run java.exe the following dialog appear:
      "The procedure entry point _JVM_LoadSystemLibrary@4 could not be located in dynamic link library jvm.dll"


      ERROR MESSAGES/STACK TRACES THAT OCCUR :
      1. add "security.provider.10=com.test.Provider" to java.security file
      2. run update
      3. update shows the warning "lib\security\java.security: Old File not found...." and after finish JRE can't work. If we run java.exe the following dialog appear:
      "The procedure entry point _JVM_LoadSystemLibrary@4 could not be located in dynamic link library jvm.dll"

      REPRODUCIBILITY :
      This bug can be reproduced always.

      Release Regression From : 6u25
      The above release value was the last known release where this
      bug was not reproducible. Since then there has been a regression.

      Release Regression From : 6u26
      The above release value was the last known release where this
      bug was not reproducible. Since then there has been a regression.

            Assignee:
            Unassigned
            Reporter:
            Nelson Dcosta (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: