IV40112: JEXTRACT ON LINUX DOES NOT LOCATE NATIVE LIBRARIES WHEN EXECUTAB LE HAS LONG NAME

APAR status

• Closed as program error.

Error description

• Error Message: jextract does not locate any native libraries:
  Creating archive file: ./core.20130304.174715.27948.0001.dmp.zip
  Adding "./core.20130304.174715.27948.0001.dmp"
  Adding "./core.20130304.174715.27948.0001.dmp.xml"
  Adding "./sdk/jre/lib/TraceFormat.dat"
  Adding "./sdk/jre/lib/J9TraceFormat.dat"
  jextract complete.
  .
  Stack Trace: N/A
  .
  

Local fix

• Collect the native libraries by hand, and submit them along with
  the jextract .zip file.
  

Problem summary

• The problem is caused when a customer launcher is used to create
  the JVM via the JNI invocation API, and the executable name is
  long.  The core file does not contain the complete executable
  name, so jextract is unable to open the executable to find out
  which native libraries should be included in the .zip file.
  

Problem conclusion

• This defect will be fixed in:
  7.0.0 SR5
  6.0.1 SR6
  6.0.0 SR14
  .
  jextract has been updated to add a new -f option.  This option
  should be used, if necesssary, to specify the full path to the
  executable.
  For example:
  jextract -f /path/to/executable core.dmp
  Then, jextract should be able to locate the native libraries.
  

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

• R260 PSY

     UP

• R600 PSY

     UP