IV43174: JVM CRASHES WHEN -DJAVA.HOME OPTION IS INVALID

APAR status

• Closed as program error.

Error description

• Error Message: Running "java -Djava.home=123" results in
  getBootClasspath failed to open file 123/lib/jars.cfg - No such
  file or directory
  Unhandled exception
  Type=Segmentation error vmState=0xffffffff
  J9Generic_Signal_Number=00000004 ExceptionCode=c0000005
  ExceptionAddress=7FC7C19D ContextFlags=00010
  03f
  Handler1=7FEFA3A0 Handler2=7FECC130 InaccessibleAddress=00000000
  EDI=0018B3EB ESI=7FBE7B30 EAX=00000000 EBX=000AC810
  ECX=7C34F797 EDX=7C38B280
  EIP=7FC7C19D ESP=0030F6F8 EBP=0018B3D8 EFLAGS=00010246
  GS=0000 FS=003B ES=0023 DS=0023
  Module=C:\prj\jvm\jre\bin\jclscar_24.dll
  Module_base_address=7FC40000 Offset_in_DLL=0003c19d
  Target=2_40_20130104_133719 (Windows XP 5.1 build 2600 Service
  Pack 3)
  CPU=x86 (1 logical CPUs) (0x7ff7c000 RAM)
  .
  Stack Trace: N/A
  .
  

Local fix

• Do not specify an invalid directory using -Djava.home
  

Problem summary

• The JVM fails to open a required file and then crashes
  

Problem conclusion

• This defect will be fixed in:
  6.0.0 SR14
  .
  The JVM has been updated to exit with an error message if the
  java.home system property specifies an invalid location
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  J9 COMMON CODE

• Fixed component ID

  620700127

Applicable component levels

• R600 PSY

     UP