Skip Headers

Oracle® JRockit Virtual Edition User's Guide Release 2.0.0 Part Number E22518-01 |
Home | Contents | Contact Us

Previous | Next
| View PDF

# 7.1 Image Tool Problems

This section provides information to help you diagnose and solve problems that might occur when you use the Oracle JRockit Virtual Edition Image Tool.

This section contains the following topics:

- How to Diagnose and Solve Image Tool Problems

- Solutions to Specific Image-Tool Errors

## 7.1.1 How to Diagnose and Solve Image Tool Problems

This section describes a roadmap that you can follow to diagnose and solve Image Tool problems efficiently.

1. Make sure that you typed the command according to the syntax specified in Appendix A, "Image Tool Command-Line Option Reference."

2. Look for a solution to the problem in the error message that is displayed (if any) when you ran the command. For most errors that occur when you use the Image Tool, the error message provides a solution.

   For example, when you use the `-c` option to create a configuration XML file and specify an XML output file that already exists, the Image Tool displays the following error message and solution:

       Writing file "myconfig.xml" ...
       error: Failed to overwrite "\myconfig.xml".
       Use the "--force" option to override the warning.

3. If the error message text does not help you diagnose and solve the problem, run the command again after including the `--log verbose` option, to see detailed messages while the command executes.

   For more information about the logging options, see -l (--log).

4. Check whether Section 7.1.2, "Solutions to Specific Image-Tool Errors" contains the solution for the problem.

5. Contact Oracle for help, as described in Section 7.3, "Contacting Oracle for Help."

## 7.1.2 Solutions to Specific Image-Tool Errors

ERROR: Unable to access jar file jrockitve-imagetool.jar

This error occurs when you run any command of the Image Tool from a directory other than the one in which you installed Oracle JRockit Virtual Edition, without specifying the full path of `jrockitve-imagetool.jar`.

Solution: Do one of the following:

- Go to the directory in which you installed the Oracle JRockit Virtual Edition, and run the command from that directory.

- In the command line, specify the path (absolute or relative) of the `jrockitve-imagetool.jar` file.

ERROR: Cannot find default <jrockitve-binary-url> at "protocol:location"

Note:

In this error message, `protocol:location` is the location (specified or default) at which the Image Tool expects to find the `jrockitve.bin` file.

The `protocol` could be `file:`, `http://`, `ftp://`, and so on. The `location` would vary accordingly.

This error occurs when you use the -a (--assemble) option, in either of the following conditions:

- The `jrockitve.bin` file is not available at the location specified in the `<jrockitve-binary-url>` element of the configuration XML file.

- The `<jrockitve-binary-url>` element is not specified in the configuration XML file, and the default location (the directory in which the configuration file resides) does not contain the `jrockitve.bin` file.

Solution: Open the configuration XML file in a text editor, and correct the path specified in the `<jrockitve-binary-url>` element. If the element does not exist, add it.

ERROR: Cannot find default <java-application-dir> at "directory_name"

This error occurs when you use the -a (--assemble) option, in either of the following conditions:

- The `<java-filesystem-imports>` element, which specifies the location of the Java application to be virtualized, is not specified in the configuration XML file, and the default location (a subdirectory named `root` within the directory in which the configuration XML file resides) does not exist.

- The files or directories specified in the `<java-filesystem-imports>` element do not exist.

Solution: Open the configuration XML file in a text editor and correct the values specified in the `<java-filesystem-imports>` element or add the element, as appropriate.

ERROR: Device or resource is busy. (File system is already mounted.)

This error occurs in the following situations:

- The Image Tool terminates unexpectedly.

  Solution: Shut down the virtual machine (if it is running), and then use the --repair option to check for and fix problems in the file system of the virtual machine image.

- You attempted to modify the image of a running virtual machine by using Image Tool options such as `-r` or `-f`.

  Solution: Shut down the virtual machine, and then perform the required modifications.