Skip to content

CAUTION: This site hosts draft documentation for the next release. For published content of the latest release, visit

Dump extractor (jpackcore)

(AIX®, Linux®, macOS®)

On some operating systems, copies of executable files and libraries are required for a full analysis of a core dump (you can get some information from the dump without these files, but not as much). Run the jpackcore utility to collect these extra files and package them into an archive file along with the core dump. To analyze the output, use the dump viewer (jdmpview).

Note: This tool replaces jextract, which is deprecated in Eclipse OpenJ9™ version 0.26.0.


jpackcore [-r] [-x] <core file name> [<zip_file>]


  • -r forces the jpackcore utility to proceed when the system dump is created from an SDK with a different build ID. See Restriction.
  • -x causes the jpackcore utility to omit the system dump itself from the archive produced. In its place, the file excluded-files.txt is added which names the excluded file.
  • <core file name> is the name of the system dump.
  • <zip_file> is the name you want to give to the processed file. If you do not specify a name, output is written to <core file name>.zip by default. The output is written to the same directory as the core file.

Restriction: You should run jpackcore on the same system that produced the system dump in order to collect the correct executables and libraries referenced in the system dump. You should also run jpackcore using the same VM level, to avoid any problems. From Eclipse OpenJ9 V0.24.0, the utility always checks that the build ID of the SDK that created the dump file matches the jpackcore build ID. Where these IDs do not match, the following exception is thrown:

J9RAS.buildID is incorrect (found XXX, expecting YYY). This version of jpackcore is incompatible with this dump (use '-r' option to relax this check).

To continue, despite the mismatch, use the -r option.

See also