IV15300: RUNTIME.EXEC RETURNS ERROR: 'INVALID UTF8 USED IN JNI FUNCTION'

APAR status

• Closed as program error.

Error description

• Error Message: IBM zOS JVM reports the error 'JVMJ9VM030E :
  Invalid UTF8 used in JNI function' and then aborted.
  .
  Stack Trace: Failing Java stack as below :
  java/lang/UNIXProcess$Gate@0x000000489B73C1D0 Owned by:
  <unowned>
  3XMTHREADINFO3  Java callstack:
  4XESTACKTRACE    at java/lang/Object.wait(Native Method)
  4XESTACKTRACE    at java/lang/Object.wait(Object.java:167)
  4XESTACKTRACE    at
  java/lang/UNIXProcess$Gate.waitForExit(UNIXProcess.java:79)
  4XESTACKTRACE    at
  java/lang/UNIXProcess.<init>(UNIXProcess.java:179)
  4XESTACKTRACE    at
  java/lang/ProcessImpl.start(ProcessImpl.java:163)
  4XESTACKTRACE    at
  java/lang/ProcessBuilder.start(ProcessBuilder.java:1032)
  4XESTACKTRACE    at java/lang/Runtime.exec(Runtime.java:626)
  4XESTACKTRACE    at java/lang/Runtime.exec(Runtime.java:494)
  Failing native stack as below :
  10       Z_COMPRESSUTF8+00000166
  11       compressUTF8+00000022
  12       Z_FINDCLASS +0000021E
  13       findClass   +00000014
  14       gpCheckFindClass+00000022
  15       checkFindClass+000000A0
  16       JNU_NewObjectByName+00000062
  17       Java_java_lang_UNIXProcess_forkAndExec+000011D0
  .
  NA
  

Local fix

• NA
  

Problem summary

• IBM JVM internally expects strings in ASCII encoding and with
  customer case it fails as it is not able understand platform
  default EBCDIC encoded strings.
  

Problem conclusion

• This defect will be fixed in:
  7.0.0 SR1
  .
  IBM JVM has been updated to handle correct string encoding to
  prevent it from abort.
  

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

  JAVA CLASS LIBS

• Fixed component ID

  620700130

Applicable component levels

• R700 PSY

     UP