The \f3appletviewer\fP command connects to the documents or resources designated by \f2urls\fP and displays each applet referenced by the documents in its own window. Note: if the documents referred to by \f2urls\fP do not reference any applets with the \f2OBJECT\fP, \f2EMBED\fP, or \f2APPLET\fP tag, then \f3appletviewer\fP does nothing. For details on the HTML tags that \f3appletviewer\fP supports, see
\f3Note:\fP The \f3appletviewer\fP requires encoded URLs according to the escaping mechanism defined in RFC2396. Only encoded URLs are supported. However, file names must be unencoded, as specified in RFC2396.
." Copyright (c) 2004, 2010, Oracle and/or its affiliates. All rights reserved.
." Copyright (c) 2004, 2011, Oracle and/or its affiliates. All rights reserved.
." DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
."
." This code is free software; you can redistribute it and/or modify it
...
...
@@ -19,7 +19,7 @@
." or visit www.oracle.com if you need additional information or have any
." questions.
."
.TH apt 1 "02 Jun 2010"
.TH apt 1 "10 May 2011"
.LP
.SH "NAME"
...
...
@@ -50,21 +50,17 @@ One or more files that list source files or other options
.SH "DESCRIPTION"
.LP
.LP
The tool \f2apt\fP, annotation processing tool, includes a set of new reflective APIs and supporting infrastructure to process program annotations. The \f2apt\fP reflective APIs provide a build\-time, source\-based, read\-only view of program structure. These reflective APIs are designed to cleanly model the Java(TM) programming language's type system after the addition of generics. First, \f2apt\fP runs annotation processors that can produce new source code and other files. Next, \f2apt\fP can cause compilation of both original and generated source files, easing development. The reflective APIs and other APIs used to interact with the tool are subpackages of \f2com.sun.mirror\fP.
\f3Note\fP: The \f2apt\fP tool and its associated API contained in the package \f2com.sun.mirror\fP have been deprecated since JDK 7 and are planned to be removed in the next major JDK release. Use the options available in the \f2javac(1)\fP tool and the APIs contained in the packages \f2javax.annotation.processing\fP and \f2javax.lang.model\fP to process annotations.
.LP
.LP
The tool \f2apt\fP, annotation processing tool, includes reflective APIs and supporting infrastructure to process program annotations. The \f2apt\fP reflective APIs provide a build\-time, source\-based, read\-only view of program structure. These reflective APIs are designed to cleanly model the Java(TM) programming language's type system after the addition of generics. First, \f2apt\fP runs annotation processors that can produce new source code and other files. Next, \f2apt\fP can cause compilation of both original and generated source files, easing development. The reflective APIs and other APIs used to interact with the tool are subpackages of \f2com.sun.mirror\fP.
.LP
.LP
A fuller discussion of how the tool operates as well as instructions for developing with \f2apt\fP are in
\f2The functionality of \fP\f2apt\fP has been subsumed by the annotation\-processing infrastructure that is now part of the \f2javac(1)\fP tool and standardized for use by all Java compilers. This new infrastructure relies on the language model and annotation\-processing APIs that are now part of the Java Platform. It is recommended that new annotation processor development be based on the new APIs and the \f2javac\fP tool.
@@ -90,6 +86,12 @@ Specify where to find annotation processor factories; if this option is used, th
.TP 3
\-factory classname
Name of annotation processor factory to use; bypasses default discovery process
.TP 3
\-version
Print version information.
.TP 3
\-X
Display information about non\-standard options.
.RE
.LP
...
...
@@ -109,10 +111,35 @@ Specify where to find user class files and annotation processor factories. If \f
.LP
Consult the javac(1) man page for information on \f2javac\fP options.
.LP
.SS
Non\-Standard Options
.LP
.RS 3
.TP 3
\-XListAnnotationTypes
List found annotation types.
.TP 3
\-XListDeclarations
List specified and included declarations.
.TP 3
\-XPrintAptRounds
Print information about initial and recursive \f2apt\fP rounds.
.TP 3
\-XPrintFactoryInfo
Print information about which annotations a factory is asked to process.
.TP 3
\-XclassesAsDecls
Treat both class and source files as declarations to process.
.RE
.LP
.LP
\f3Note\fP: Because these options are non\-standard, they are subject to change without notice.
.LP
.SH "NOTES"
.LP
.LP
The functionality of \f2apt\fP has been subsumed by the standard annotation\-processing infrastructure now offered by \f2javac\fP. Support for \f2apt\fP and its associated APIs may be discontinued in some future JDK release.
The \f2apt\fP tool and its associated API contained in the package \f2com.sun.mirror\fP have been deprecated since JDK 7 and are planned to be removed in the next major JDK release. Use the options available in the \f2javac(1)\fP tool and the APIs contained in the packages \f2javax.annotation.processing\fP and \f2javax.lang.model\fP to process annotations.
The \f3extcheck\fP utility checks a specified Jar file for title and version conflicts with any extensions installed in the Java(TM) SDK. Before installing an extension, you can use this utility to see if the same or a more recent version of the extension is already installed.
...
...
@@ -62,8 +54,6 @@ If no conflict is detected, the return code is \f20\fP.
If the manifest of any jar file in the extensions directory has the same \f2Specification\-title\fP and the same or a newer \f2Specification\-version\fP number, a non\-zero error code is returned. A non\-zero error code is also returned if \f2targetfile.jar\fP does not have the \f2Specification\-title\fP or \f2Specification\-version\fP attributes in its manifest.
.LP
.SH "OPTIONS"
.LP
.LP
.RS 3
.TP 3
...
...
@@ -76,8 +66,6 @@ Pass \f2option\fP to the Java virtual machine, where \f2option\fP is one of the
." Copyright (c) 1997, 2010, Oracle and/or its affiliates. All rights reserved.
." Copyright (c) 1997, 2011, Oracle and/or its affiliates. All rights reserved.
." DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
."
." This code is free software; you can redistribute it and/or modify it
...
...
@@ -19,7 +19,7 @@
." or visit www.oracle.com if you need additional information or have any
." questions.
."
.TH jar 1 "02 Jun 2010"
.TH jar 1 "10 May 2011"
.LP
.SH "Name"
...
...
@@ -27,8 +27,6 @@ jar\-The Java Archive Tool
.LP
\f3jar\fP combines multiple files into a single JAR archive file.
.SH "SYNOPSIS"
.LP
.LP
.RS 3
.TP 3
...
...
@@ -51,9 +49,6 @@ Add index to jar file
.LP
.LP
where:
.LP
.RS 3
.LP
.RS 3
.TP 3
...
...
@@ -80,10 +75,7 @@ Option to be passed into the Java runtime environment. (There must be no space b
.RE
.LP
.RE
.SH "DESCRIPTION"
.LP
.LP
The \f3jar\fP tool combines multiple files into a single JAR archive file. \f3jar\fP is a general\-purpose archiving and compression tool, based on ZIP and the
.na
...
...
@@ -92,9 +84,6 @@ The \f3jar\fP tool combines multiple files into a single JAR archive file. \f3ja
http://www.gzip.org/zlib/ compression format. However, \f3jar\fP was designed mainly package java applets or applications into a single archive. When the components of an applet or application (files, images and sounds) are combined into a single archive, they can be downloaded by a java agent (like a browser) in a single HTTP transaction, rather than requiring a new connection for each piece. This dramatically improves download times. \f3jar\fP also compresses files and so further improves download time. In addition, it allows individual entries in a file to be signed by the applet author so that their origin can be authenticated. The syntax for the jar tool is almost identical to the syntax for the \f2tar\fP command. A \f3jar\fP archive can be used as a class path entry, whether or not it is compressed.
.LP
Typical usage to combine files into a jar file is:
.LP
.RS 3
.LP
.nf
\f3
...
...
@@ -103,19 +92,15 @@ Typical usage to combine files into a jar file is:
.fl
\fP
.fi
.RE
.LP
In this example, all the class files in the current directory are placed into the file named \f2myFile.jar\fP. The jar tool automatically generates a manifest file entry named \f2META\-INF/MANIFEST.MF\fP. It is always the first entry in the jar file. The manifest file declares meta\-information about the archive, and stores that data as \f2name\ :\ value\fP pairs. Refer to the
.na
\f2JAR file specification\fP @
.fi
http://java.sun.com/javase/6/docs/technotes/guides/jar/jar.html#JAR%20Manifest for details explaining how the jar tool stores meta\-information in the manifest file.
http://download.oracle.com/javase/7/docs/technotes/guides/jar/jar.html#JAR%20Manifest for details explaining how the jar tool stores meta\-information in the manifest file.
.LP
If a jar file should include \f2name\ :\ value\fP pairs contained in an existing manifest file, specify that file using the \f2\-m\fP option:
.LP
.RS 3
.LP
.nf
\f3
...
...
@@ -124,7 +109,6 @@ If a jar file should include \f2name\ :\ value\fP pairs contained in an existing
.fl
\fP
.fi
.RE
.LP
An existing manifest file must end with a new line character.\ \f3jar\fP does not parse the last line of a manifest file if it does not end with a new line character.
...
...
@@ -135,9 +119,6 @@ An existing manifest file must end with a new line character.\ \f3jar\fP does n
.LP
\f3Note:\ \fP A jar command that specifies \f2cfm\fP on the command line instead of \f2cmf\fP (the order of the m and \-f options are reversed), the \f3jar\fP command line must specify the name of the jar archive first, followed by the name of the manifest file:
.RS 3
.LP
.nf
\f3
.fl
...
...
@@ -145,15 +126,11 @@ An existing manifest file must end with a new line character.\ \f3jar\fP does n
.fl
\fP
.fi
.RE
.LP
The manifest is in a text format inspired by RFC822 ASCII format, so it is easy to view and process manifest\-file contents.
.LP
To extract the files from a jar file, use \f2x\fP:
.LP
.RS 3
.LP
.nf
\f3
...
...
@@ -162,14 +139,10 @@ To extract the files from a jar file, use \f2x\fP:
.fl
\fP
.fi
.RE
.LP
.LP
To extract individual files from a jar file, supply their filenames:
.LP
.RS 3
.LP
.nf
\f3
...
...
@@ -178,7 +151,6 @@ To extract individual files from a jar file, supply their filenames:
.fl
\fP
.fi
.RE
.LP
.LP
...
...
@@ -186,10 +158,7 @@ Beginning with version 1.3 of the JDK, the \f2jar\fP utility supports
.na
\f2JarIndex\fP @
.fi
http://java.sun.com/javase/6/docs/technotes/guides/jar/jar.html#JAR%20Index, which allows application class loaders to load classes more efficiently from jar files. If an application or applet is bundled into multiple jar files,\ only the necessary jar files will be downloaded and opened to load classes. This performance optimization is enabled by running \f2jar\fP with the \f2\-i\fPoption. It will generate package location information for the specified main jar file and all the jar files it depends on, which need to be specified in the \f2Class\-Path\fP attribute of the main jar file's manifest.
.LP
.RS 3
http://download.oracle.com/javase/7/docs/technotes/guides/jar/jar.html#JAR_Index, which allows application class loaders to load classes more efficiently from jar files. If an application or applet is bundled into multiple jar files,\ only the necessary jar files will be downloaded and opened to load classes. This performance optimization is enabled by running \f2jar\fP with the \f2\-i\fPoption. It will generate package location information for the specified main jar file and all the jar files it depends on, which need to be specified in the \f2Class\-Path\fP attribute of the main jar file's manifest.
@@ -209,9 +177,6 @@ The application class loader uses the information stored in this file for effici
.br
.br
To copy directories, first compress files in \f2dir1\fP to \f2stdout\fP, then extract from \f2stdin\fP to \f2dir2\fP (omitting the \f2\-f\fP option from both \f2jar\fP commands):
.LP
.RS 3
.LP
.nf
\f3
...
...
@@ -220,7 +185,6 @@ To copy directories, first compress files in \f2dir1\fP to \f2stdout\fP, then ex
.fl
\fP
.fi
.RE
.LP
.LP
...
...
@@ -228,11 +192,9 @@ To review command samples which use \f2jar\fP to opeate on jar files and jar fil
@@ -241,9 +203,6 @@ Creates a new archive file named \f2jarfile\fP (if \f2f\fP is specified) or to s
.TP 3
u
Updates an existing file \f2jarfile\fP (when \f2f\fP is specified) by adding to it files and directories specified by \f2inputfiles\fP. For example:
.RS 3
.LP
.nf
\f3
.fl
...
...
@@ -251,11 +210,7 @@ jar uf foo.jar foo.class
.fl
\fP
.fi
.RE
would add the file \f2foo.class\fP to the existing jar file \f2foo.jar\fP. The \f2\-u\fP option can also update the manifest entry, as given by this example:
.RS 3
.LP
.nf
\f3
.fl
...
...
@@ -263,7 +218,6 @@ jar umf manifest foo.jar
.fl
\fP
.fi
.RE
updates the \f2foo.jar\fP manifest with the \f2name : value\fP pairs in \f2manifest\fP.
.TP 3
x
...
...
@@ -274,9 +228,6 @@ Lists the table of contents from \f2jarfile\fP (if \f2f\fP is specified) or stan
.TP 3
i
Generate index information for the specified \f2jarfile\fP and its dependent jar files. For example:
.RS 3
.LP
.nf
\f3
.fl
...
...
@@ -284,7 +235,6 @@ jar i foo.jar
.fl
\fP
.fi
.RE
.LP
would generate an \f2INDEX.LIST\fP file in \f2foo.jar\fP which contains location information for each package in \f2foo.jar\fP and all the jar files specified in the \f2Class\-Path\fP attribute of \f2foo.jar\fP. See the index example.
.TP 3
...
...
@@ -302,11 +252,9 @@ Do not create a manifest file entry (for c and u), or delete a manifest file ent
.TP 3
m
Includes \f2name : value\fP attribute pairs from the specified manifest file \f2manifest\fP in the file at \f2META\-INF/MANIFEST.MF\fP. \f2jar\fP adds a \f2name\ :\ value\fP pair unless an entry already exists with the same name, in which case \f2jar\fP updates its value.
.LP
.br
.br
On the command line, the letters \f3m\fP and \f3f\fP must appear in the same order that \f2manifest\fP and \f2jarfile\fP appear. Example use:
.RS 3
.LP
.nf
\f3
.fl
...
...
@@ -314,22 +262,18 @@ jar cmf myManifestFile myFile.jar *.class
.fl
\fP
.fi
.RE
You can add special\-purpose \f2name\ :\ value\fP attribute pairs to the manifest that aren't contained in the default manifest. For example, you can add attributes specifying vendor information, version information, package sealing, or to make JAR\-bundled applications executable. See the
.na
\f2JAR Files\fP @
.fi
http://java.sun.com/docs/books/tutorial/jar/ trail in the Java Tutorial for examples of using the \f4\-m\fP option.
.LP
http://download.oracle.com/javase/tutorial/deployment/jar/ trail in the Java Tutorial for examples of using the \f4\-m\fP option.
.TP 3
e
Sets \f2entrypoint\fP as the application entry point for stand\-alone applications bundled into executable jar file. The use of this option creates or overrides the \f2Main\-Class\fP attribute value in the manifest file. This option can be used during creation of jar file or while updating the jar file. This option specifies the application entry point without editing or creating the manifest file.
.br
.br
.br
For example, this command creates \f2Main.jar\fP where the \f2Main\-Class\fP attribute value in the manifest is set to \f2Main\fP:
.RS 3
.LP
.nf
\f3
.fl
...
...
@@ -337,12 +281,7 @@ jar cfe Main.jar Main Main.class
.fl
\fP
.fi
.RE
.LP
The java runtime can directly invoke this application by running the following command:
.RS 3
.LP
.nf
\f3
.fl
...
...
@@ -350,11 +289,7 @@ java \-jar Main.jar
.fl
\fP
.fi
.RE
If the entrypoint class name is in a package it may use either a dot (".") or slash ("/") character as the delimiter. For example, if \f2Main.class\fP is in a package called \f2foo\fP the entry point can be specified in the following ways:
.RS 3
.LP
.nf
\f3
.fl
...
...
@@ -362,11 +297,7 @@ jar \-cfe Main.jar foo/Main foo/Main.class
.fl
\fP
.fi
.RE
or
.RS 3
.LP
.nf
\f3
.fl
...
...
@@ -374,18 +305,13 @@ jar \-cfe Main.jar foo.Main foo/Main.class
.fl
\fP
.fi
.RE
\f3Note:\ \fP specifying both \f2\-m\fP and \f2\-e\fP options together when the given manifest also contains the \f2Main\-Class\fP attribute results in an ambigous \f2Main.class\fP specification, leading to an error and the jar creation or update operation is aborted.
.LP
.TP 3
\-C\ dir
\-C\ dir
Temporarily changes directories (\f2cd\fP\ \f2dir\fP) during execution of the \f2jar\fP command while processing the following \f2inputfiles\fP argument. Its operation is intended to be similar to the \f2\-C\fP option of the UNIX \f2tar\fP utility.
.br
.br
For example, this command changes to the \f2classes\fP directory and adds the \f2bar.class\fP from that directory to \f2foo.jar\fP:
.RS 3
.LP
.nf
\f3
.fl
...
...
@@ -393,11 +319,7 @@ jar uf foo.jar \-C classes bar.class
.fl
\fP
.fi
.RE
This command changes to the \f2classes\fP directory and adds to \f2foo.jar\fP all files within the \f2classes\fP directory (without creating a classes directory in the jar file), then changes back to the original directory before changing to the \f2bin\fP directory to add \f2xyz.class\fP to \f2foo.jar\fP.
.RS 3
.LP
.nf
\f3
.fl
...
...
@@ -405,11 +327,7 @@ jar uf foo.jar \-C classes . \-C bin xyz.class
.fl
\fP
.fi
.RE
If \f2classes\fP holds files \f2bar1\fP and \f2bar2\fP, then here's what the jar file will contain using \f2jar tf foo.jar\fP:
.RS 3
.LP
.nf
\f3
.fl
...
...
@@ -425,7 +343,6 @@ xyz.class
.fl
\fP
.fi
.RE
.LP
.TP 3
\-Joption
...
...
@@ -434,8 +351,6 @@ Pass \f2option\fP to the Java runtime environment, where \f2option\fP is one of
.LP
.SH "COMMAND LINE ARGUMENT FILES"
.LP
.LP
To shorten or simplify the jar command line, you can specify one or more files that themselves contain arguments to the \f2jar\fP command (except \f2\-J\fP options). This enables you to create jar commands of any length, overcoming command line limits imposed by the operating system.
.LP
...
...
@@ -446,9 +361,6 @@ When executing \f2jar\fP, pass in the path and name of each argument file with t
.br
.br
The example below, \f2classes.list\fP holds the names of files output by a \f2find\fP command:
.LP
.RS 3
.LP
.nf
\f3
...
...
@@ -456,14 +368,10 @@ The example below, \f2classes.list\fP holds the names of files output by a \f2fi
You can then execute the \f2jar\fP command on \f2Classes.list\fP by passing it to \f2jar\fP using argfile syntax:
.LP
.RS 3
.LP
.nf
\f3
...
...
@@ -472,13 +380,9 @@ You can then execute the \f2jar\fP command on \f2Classes.list\fP by passing it t
.fl
\fP
.fi
.RE
.LP
An argument file can specify a path, but any filenames inside the argument file that have relative paths are relative to the current working directory, not to the path passed in. Here is an example:
.RS 3
.LP
.nf
\f3
.fl
...
...
@@ -486,20 +390,14 @@ An argument file can specify a path, but any filenames inside the argument file
.fl
\fP
.fi
.RE
.LP
.LP
.LP
.SH "EXAMPLES"
.LP
.LP
To add all the files in a particular directory to an archive (overwriting contents if the archive already exists). Enumerating verbosely (with the \f2\-v\fP option) will tell you more information about the files in the archive, such as their size and last modified date.
To see the entry names in the jarfile, use the \f2t\fP option:
.RS 3
.LP
.nf
\f3
.fl
...
...
@@ -619,7 +509,6 @@ images/at_work.gif
.fl
\fP
.fi
.RE
.LP
.LP
...
...
@@ -629,9 +518,6 @@ To add an index file to the jar file for speeding up class loading, use the \f2i
Example:
.br
.LP
.RS 3
.LP
If you split the inter\-dependent classes for a stock trade application into three jar files: \f2main.jar\fP, \f2buy.jar\fP, and \f2sell.jar\fP.
.br
...
...
@@ -661,37 +547,33 @@ then you can use the \f2\-i\fP option to speed up the class loading time for you
.LP
An \f2INDEX.LIST\fP file is inserted to the \f2META\-INF\fP directory. This enables the application class loader to download the specified jar files when it is searching for classes or resources.
." Copyright (c) 1994, 2010, Oracle and/or its affiliates. All rights reserved.
." Copyright (c) 1994, 2011, Oracle and/or its affiliates. All rights reserved.
." DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
."
." This code is free software; you can redistribute it and/or modify it
...
...
@@ -19,7 +19,7 @@
." or visit www.oracle.com if you need additional information or have any
." questions.
."
.TH java 1 "02 Jun 2010"
.TH java 1 "10 May 2011"
.LP
.SH "Name"
...
...
@@ -36,9 +36,6 @@ java \- the Java application launcher
.fl
.fi
.LP
.RS 3
.LP
.RS 3
.TP 3
...
...
@@ -56,10 +53,7 @@ Argument passed to the \f3main\fP function.
.RE
.LP
.RE
.SH "DESCRIPTION"
.LP
.LP
.LP
The \f3java\fP tool launches a Java application. It does this by starting a Java runtime environment, loading a specified class, and invoking that class's \f3main\fP method.
...
...
@@ -70,7 +64,7 @@ The method must be declared public and static, it must not return any value, and
.nf
\f3
.fl
public static void main(String args[])
public static void main(String args[])
.fl
\fP
.fi
...
...
@@ -86,77 +80,80 @@ The Java runtime searches for the startup class, and other classes used, in thre
Non\-option arguments after the class name or JAR file name are passed to the \f3main\fP function.
.LP
.SH "OPTIONS"
.LP
.LP
.LP
The launcher has a set of standard options that are supported on the current runtime environment and will be supported in future releases. In addition, the current implementations of the virtual machines support a set of non\-standard options that are subject to change in future releases.
.LP
.SH "Standard Options"
.LP
.LP
.RS 3
.TP 3
\-client
.LP
Select the Java HotSpot Client VM. A 64\-bit capable jdk currently ignores this option and instead uses the Java Hotspot Server VM.
Specify a list of directories, JAR archives, and ZIP archives to search for class files. Class path entries are separated by colons (\f3:\fP). Specifying \f3\-classpath\fP or \f3\-cp\fP overrides any setting of the \f3CLASSPATH\fP environment variable.
.LP
.br
.br
If \f3\-classpath\fP and \f3\-cp\fP are not used and \f3CLASSPATH\fP is not set, the user class path consists of the current directory (\f4.\fP).
.LP
.br
.br
As a special convenience, a class path element containing a basename of \f2*\fP is considered equivalent to specifying a list of all the files in the directory with the extension \f2.jar\fP or \f2.JAR\fP (a java program cannot tell the difference between the two invocations).
.br
.br
For example, if directory \f2foo\fP contains \f2a.jar\fP and \f2b.JAR\fP, then the class path element \f2foo/*\fP is expanded to a \f2A.jar:b.JAR\fP, except that the order of jar files is unspecified. All jar files in the specified directory, even hidden ones, are included in the list. A classpath entry consisting simply of \f2*\fP expands to a list of all the jar files in the current directory. The \f2CLASSPATH\fP environment variable, where defined, will be similarly expanded. Any classpath wildcard expansion occurs before the Java virtual machine is started \-\- no Java program will ever see unexpanded wildcards except by querying the environment. For example; by invoking \f2System.getenv("CLASSPATH")\fP.
@@ -165,18 +162,22 @@ Set a system property value.
.TP 3
\-d64
Request that the program to be run in a 32\-bit or 64\-bit environment, respectively. If the requested environment is not installed or is not supported, an error is reported.
.LP
.br
.br
Currently only the Java HotSpot Server VM supports 64\-bit operation, and the "\-server" option is implicit with the use of \-d64. And the "\-client" option is ignored with the use of \-d64. This is subject to change in a future release.
.LP
.br
.br
If neither \f3\-d32\fP nor \f3\-d64\fP is specified, the default is to run in a 32\-bit environment, except for 64\-bit only systems. This is subject to change in a future release.
Enable assertions. Assertions are disabled by default.
.LP
.br
.br
With no arguments, \f3enableassertions\fP or \f3\-ea\fP enables assertions. With one argument ending in \f2"..."\fP, the switch enables assertions in the specified package and any subpackages. If the argument is simply \f2"..."\fP, the switch enables assertions in the unnamed package in the current working directory. With one argument not ending in \f2"..."\fP, the switch enables assertions in the specified class.
.LP
.br
.br
If a single command line contains multiple instances of these switches, they are processed in order before loading any classes. So, for example, to run a program with assertions enabled only in package \f2com.wombat.fruitbat\fP (and any subpackages), the following command could be used:
The \f3\-enableassertions\fP and \f3\-ea\fP switches apply to \f2all\fP class loaders and to system classes (which do not have a class loader). There is one exception to this rule: in their no\-argument form, the switches do \f2not\fP apply to system. This makes it easy to turn on asserts in all classes except for system classes. A separate switch is provided to enable asserts in all system classes; see \f3\-enablesystemassertions\fP below.
With no arguments, \f3disableassertions\fP or \f3\-da\fP disables assertions. With one argument ending in \f2"..."\fP, the switch disables assertions in the specified package and any subpackages. If the argument is simply \f2"..."\fP, the switch disables assertions in the unnamed package in the current working directory. With one argument not ending in \f2"..."\fP, the switch disables assertions in the specified class.
.LP
.br
.br
To run a program with assertions enabled in package \f2com.wombat.fruitbat\fP but disabled in class \f2com.wombat.fruitbat.Brickbat\fP, the following command could be used:
The \f3\-disableassertions\fP and \f3\-da\fP switches apply to \f2all\fP class loaders and to system classes (which do not have a class loader). There is one exception to this rule: in their no\-argument form, the switches do \f2not\fP apply to system. This makes it easy to turn on asserts in all classes except for system classes. A separate switch is provided to enable asserts in all system classes; see \f3\-disablesystemassertions\fP below.
.TP 3
\-enablesystemassertions
...
...
@@ -215,29 +216,36 @@ Enable asserts in all system classes (sets the \f2default assertion status\fP fo
.TP 3
\-dsa
Disables asserts in all system classes.
.LP
.TP 3
\-jar
Execute a program encapsulated in a JAR file. The first argument is the name of a JAR file instead of a startup class name. In order for this option to work, the manifest of the JAR file must contain a line of the form \f3Main\-Class: \fP\f4classname\fP. Here, \f2classname\fP identifies the class having the \f2public\ static\ void\ main(String[]\ args)\fP method that serves as your application's starting point. See the jar(1) and the Jar trail of the
.na
\f2Java Tutorial\fP @
.fi
http://java.sun.com/docs/books/tutorial/jar for information about working with Jar files and Jar\-file manifests.
.LP
http://download.oracle.com/javase/tutorial/deployment/jar for information about working with Jar files and Jar\-file manifests.
.br
.br
When you use this option, the JAR file is the source of all user classes, and other user class path settings are ignored.
.LP
.br
.br
Note that JAR files that can be run with the "java \-jar" option can have their execute permissions set so they can be run without using "java \-jar". Refer to
@@ -255,7 +263,8 @@ Display version information and exit.
.TP 3
\-version:release
Specifies that the version specified by \f2release\fP is required by the class or jar file specified on the command line. If the version of the java command invoked does not meet this specification and an appropriate implementation is found on the system, the appropriate implementation will be used.
.LP
.br
.br
\f2release\fP not only can specify an exact version, but can also specify a list of versions called a version string. A version string is an ordered list of version ranges separated by spaces. A version range is either a version\-id, a version\-id followed by a star (*), a version\-id followed by a plus sign (+) , or two version\-ranges combined using an ampersand (&). The star means prefix match, the plus sign means this version or greater, and the ampersand means the logical anding of the two version\-ranges. For example:
.nf
\f3
...
...
@@ -265,9 +274,11 @@ Specifies that the version specified by \f2release\fP is required by the class o
\fP
.fi
The meaning of the above is that the class or jar file requires either version 1.6.0_13, or a version with 1.6 as a version\-id prefix and that is not less than 1.6.0_10.. The exact syntax and definition of version strings may be found in Appendix A of the Java Network Launching Protocol & API Specification (JSR\-56).
.LP
.br
.br
For jar files, the usual preference is to specify version requirements in the jar file manifest rather than on the command line.
.LP
.br
.br
See the following NOTES section for important policy information on the use of this option.
.TP 3
\-showversion
...
...
@@ -278,6 +289,9 @@ Display version information and continue.
\-help
Display usage information and exit.
.TP 3
\-splash:imagepath
Show splash screen with image specified by \f2imagepath\fP.
.TP 3
\-X
Display information about non\-standard options and exit.
.RE
...
...
@@ -285,9 +299,6 @@ Display information about non\-standard options and exit.
.LP
.SS
Non\-Standard Options
.LP
.RS 3
.LP
.RS 3
.TP 3
...
...
@@ -320,17 +331,19 @@ Enable the incremental garbage collector. The incremental garbage collector, whi
.TP 3
\-Xloggc:file
Report on each garbage collection event, as with \-verbose:gc, but log this data to \f2file\fP. In addition to the information \f2\-verbose:gc\fP gives, each reported event will be preceeded by the time (in seconds) since the first garbage\-collection event.
.LP
.br
.br
Always use a local file system for storage of this file to avoid stalling the JVM due to network latency. The file may be truncated in the case of a full file system and logging will continue on the truncated file. This option overrides \f2\-verbose:gc\fP if both are given on the command line.
.LP
.TP 3
\-Xmsn
Specify the initial size, in bytes, of the memory allocation pool. This value must be a multiple of 1024 greater than 1MB. Append the letter \f2k\fP or \f2K\fP to indicate kilobytes, or \f2m\fP or \f2M\fP to indicate megabytes. The default value is chosen at runtime based on system configuration. For more information, see HotSpot Ergonomics
Specify the initial size, in bytes, of the memory allocation pool. This value must be a multiple of 1024 greater than 1MB. Append the letter \f2k\fP or \f2K\fP to indicate kilobytes, or \f2m\fP or \f2M\fP to indicate megabytes. The default value is chosen at runtime based on system configuration. For more information, see
Specify the maximum size, in bytes, of the memory allocation pool. This value must a multiple of 1024 greater than 2MB. Append the letter \f2k\fP or \f2K\fP to indicate kilobytes, or \f2m\fP or \f2M\fP to indicate megabytes. The default value is chosen at runtime based on system configuration. For more information, see HotSpot Ergonomics
Specify the maximum size, in bytes, of the memory allocation pool. This value must a multiple of 1024 greater than 2MB. Append the letter \f2k\fP or \f2K\fP to indicate kilobytes, or \f2m\fP or \f2M\fP to indicate megabytes. The default value is chosen at runtime based on system configuration. For more information, see
On Solaris 7 and Solaris 8 SPARC platforms, the upper limit for this value is approximately 4000m minus overhead amounts. On Solaris 2.6 and x86 platforms, the upper limit is approximately 2000m minus overhead amounts. On Linux platforms, the upper limit is approximately 2000m minus overhead amounts.
.TP 3
\-Xprof
Profiles the running program, and sends profiling data to standard output. This option is provided as a utility that is useful in program development and is not intended to be used in production systems.
.LP
.TP 3
\-Xrs
Reduces use of operating\-system signals by the Java virtual machine (JVM).
.LP
.br
.br
In a previous release, the Shutdown Hooks facility was added to allow orderly shutdown of a Java application. The intent was to allow user cleanup code (such as closing database connections) to run at shutdown, even if the JVM terminates abruptly.
.LP
.br
.br
Sun's JVM catches signals to implement shutdown hooks for abnormal JVM termination. The JVM uses SIGHUP, SIGINT, and SIGTERM to initiate the running of shutdown hooks.
.LP
.br
.br
The JVM uses a similar mechanism to implement the pre\-1.2 feature of dumping thread stacks for debugging purposes. Sun's JVM uses SIGQUIT to perform thread dumps.
.LP
.br
.br
Applications embedding the JVM frequently need to trap signals like SIGINT or SIGTERM, which can lead to interference with the JVM's own signal handlers. The \f3\-Xrs\fP command\-line option is available to address this issue. When \f3\-Xrs\fP is used on Sun's JVM, the signal masks for SIGINT, SIGTERM, SIGHUP, and SIGQUIT are not changed by the JVM, and signal handlers for these signals are not installed.
.LP
.br
.br
There are two consequences of specifying \f3\-Xrs\fP:
.RS 3
.TP 2
...
...
@@ -402,12 +419,11 @@ The VM uses \f2SIGUSR1\fP and \f2SIGUSR2\fP by default, which can sometimes conf
.RE
.LP
.RE
.SH "NOTES"
.LP
.LP
The \f3\-version:\fP\f2release\fP command line option places no restrictions on the complexity of the release specification. However, only a restricted subset of the possible release specifications represent sound policy and only these are fully supported. These policies are:
.LP
.RS 3
.TP 3
1.
...
...
@@ -422,8 +438,7 @@ Any version greater than an arbitrarily precise version\-id. For example:
.fl
\fP
.fi
.LP
Would utilize any version greater than 1.6.0_10. This is useful for a case where an interface was introduced (or a bug fixed) in the release specified.
This would utilize any version greater than \f21.6.0_10\fP. This is useful for a case where an interface was introduced (or a bug fixed) in the release specified.
.TP 3
3.
A version greater than an arbitrarily precise version\-id, bounded by the upper bound of that release family. For example:
...
...
@@ -448,9 +463,22 @@ Similar to item 2. this is useful when a change was introduced in a release (1.7
.RE
.LP
.SH "SEE ALSO"
.SH "EXIT STATUS"
.LP
.LP
The following exit values are generally returned by the launcher, typically when the launcher is called with the wrong arguments, serious errors, or exceptions thrown from the Java Virtual Machine. However, a Java application may choose to return any value using the API call \f2System.exit(exitValue)\fP.
." Copyright (c) 1994, 2010, Oracle and/or its affiliates. All rights reserved.
." Copyright (c) 1994, 2011, Oracle and/or its affiliates. All rights reserved.
." DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
."
." This code is free software; you can redistribute it and/or modify it
...
...
@@ -19,37 +19,27 @@
." or visit www.oracle.com if you need additional information or have any
." questions.
."
.TH javah 1 "02 Jun 2010"
.TH javah 1 "10 May 2011"
.LP
.SH "Name"
javah \- C Header and Stub File Generator
.LP
.RS 3
.LP
.LP
\f3javah\fP produces C header files and C source files from a Java class. These files provide the connective glue that allow your Java and C code to interact.
\f3javah\fP generates C header and source files that are needed to implement native methods. The generated header and source files are used by C programs to reference an object's instance variables from native source code. The .h file contains a struct definition whose layout parallels the layout of the corresponding class. The fields in the struct correspond to instance variables in the class.
...
...
@@ -63,12 +53,7 @@ By default \f3javah\fP creates a header file for each class listed on the comman
.LP
The new native method interface, Java Native Interface (JNI), does not require header information or stub files. \f3javah\fP can still be used to generate native method function proptotypes needed for JNI\-style native methods. \f3javah\fP produces JNI\-style output by default, and places the result in the .h file.
.LP
.LP
\f3javah_g\fP is a non\-optimized version of \f3javah\fP suitable for use with debuggers like jdb(1).
.LP
.SH "OPTIONS"
.LP
.LP
.RS 3
.TP 3
...
...
@@ -110,7 +95,6 @@ For example:
.fl
\fP
.fi
.LP
As a special convenience, a class path element containing a basename of \f2*\fP is considered equivalent to specifying a list of all the files in the directory with the extension \f2.jar\fP or \f2.JAR\fP (a java program cannot tell the difference between the two invocations).
.br
.br
...
...
@@ -131,8 +115,6 @@ Pass \f2option\fP to the Java virtual machine, where \f2option\fP is one of the
.LP
.SH "ENVIRONMENT VARIABLES"
.LP
.LP
.RS 3
.TP 3
...
...
@@ -149,8 +131,6 @@ Used to provide the system a path to user\-defined classes. Directories are sepa
." Copyright (c) 1994, 2010, Oracle and/or its affiliates. All rights reserved.
." Copyright (c) 1994, 2011, Oracle and/or its affiliates. All rights reserved.
." DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
."
." This code is free software; you can redistribute it and/or modify it
...
...
@@ -19,41 +19,43 @@
." or visit www.oracle.com if you need additional information or have any
." questions.
."
.TH javap 1 "02 Jun 2010"
.TH javap 1 "10 May 2011"
.LP
.SH "Name"
javap \- The Java Class File Disassembler
.LP
.RS 3
.LP
.LP
Disassembles class files.
.LP
.RE
.SH "SYNOPSIS"
.LP
.LP
.nf
\f3
.fl
javap [ \fP\f3options\fP\f3 ] class. . .
javap [ \fP\f3options\fP\f3 ] classes
.fl
\fP
.fi
.LP
.SH "DESCRIPTION"
.LP
.LP
.LP
The \f3javap\fP command disassembles a class file. Its output depends on the options used. If no options are used, \f3javap\fP prints out the package, protected, and public fields and methods of the classes passed to it. \f3javap\fP prints its output to stdout. For example, compile the following class declaration:
The \f3javap\fP command disassembles one or more class files. Its output depends on the options used. If no options are used, \f3javap\fP prints out the package, protected, and public fields and methods of the classes passed to it. \f3javap\fP prints its output to stdout.
.LP
.RS 3
.TP 3
options
Command\-line options.
.TP 3
classes
List of one or more classes (separated by spaces) to be processed for annotations (such as \f2DocFooter.class\fP). You may specify a class that can be found in the class path, by its file name (for example, \f2/home/user/myproject/src/DocFooter.class\fP), or with a URL (for example, \f2file:///home/user/myproject/src/DocFooter.class\fP).
.RE
.LP
.LP
For example, compile the following class declaration:
.LP
.nf
\f3
...
...
@@ -96,19 +98,15 @@ public class DocFooter extends Applet {
.fl
\fP
.fi
.RE
.LP
.LP
The output from \f3javap DocFooter\fP yields:
.LP
.RS 3
The output from \f3javap DocFooter.class\fP yields:
.LP
.nf
\f3
.fl
Compiled from DocFooter.java
Compiled from "DocFooter.java"
.fl
public class DocFooter extends java.applet.Applet {
.fl
...
...
@@ -126,136 +124,134 @@ public class DocFooter extends java.applet.Applet {
.fl
\fP
.fi
.RE
.LP
.LP
The output from \f3javap \-c DocFooter\fP yields:
.LP
.RS 3
The output from \f3javap \-c DocFooter.class\fP yields:
.LP
.nf
\f3
.fl
Compiled from DocFooter.java
Compiled from "DocFooter.java"
.fl
public class DocFooter extends java.applet.Applet {
Shows system information (path, size, date, MD5 hash) of the class being processed.
.TP 3
\-constants
Shows static final constants.
.TP 3
\-c
Prints out disassembled code, i.e., the instructions that comprise the Java bytecodes, for each of the methods in the class. These are documented in the
Prints stack size, number of \f2locals\fP and \f2args\fP for methods.
.TP 3
\-classpath path
Specifies the path \f3javap\fP uses to look up classes. Overrides the default or the CLASSPATH environment variable if it is set. Directories are separated by colons. Thus the general format for \f2path\fP is:
.nf
\f3
.fl
.:<your_path>
.fl
\fP
.fi
For example:
.nf
\f3
.fl
.:/home/avh/classes:/usr/local/java/classes
.fl
\fP
.fi
Specifies the path \f3javap\fP uses to look up classes. Overrides the default or the CLASSPATH environment variable if it is set.
.TP 3
\-bootclasspath path
Specifies path from which to load bootstrap classes. By default, the bootstrap classes are the classes implementing the core Java platform located in \f2jre/lib/rt.jar\fP and several other jar files.
...
...
@@ -325,32 +308,8 @@ Specifies path from which to load bootstrap classes. By default, the bootstrap c
Overrides location at which installed extensions are searched for. The default location for extensions is the value of \f2java.ext.dirs\fP.
.RE
.LP
.SH "ENVIRONMENT VARIABLES"
.LP
.LP
.RS 3
.TP 3
CLASSPATH
Used to provide the system a path to user\-defined classes. Directories are separated by colons, for example, For example:
." Copyright (c) 2003, 2010, Oracle and/or its affiliates. All rights reserved.
." Copyright (c) 2003, 2011, Oracle and/or its affiliates. All rights reserved.
." DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
."
." This code is free software; you can redistribute it and/or modify it
...
...
@@ -19,30 +19,18 @@
." or visit www.oracle.com if you need additional information or have any
." questions.
."
.TH javaws 1 "02 Jun 2010"
.TH javaws 1 "10 May 2011"
.LP
.SH "Name"
\f2javaws\fP Command Line
.LP
.LP
\
.LP
.SS
NAME
.LP
.RS 3
.SH "NAME"
.LP
.LP
\f2javaws\fP \- Java Web Start launcher command
.LP
.RE
.SS
SYNOPSIS
.LP
.RS 3
.SH "SYNOPSIS"
.LP
.LP
\f2javaws [run\-options] <jnlp>\fP
...
...
@@ -50,49 +38,27 @@ SYNOPSIS
.LP
\f2javaws [control\-options]\fP
.LP
.RE
.SS
PARAMETERS
.LP
.RS 3
.SH "PARAMETERS"
.LP
.LP
\f2[run\-options]\fP
.LP
.RS 3
.LP
.LP
Command\-line run\-options. run\-options may be in any order. For a discussion of the various run\-options, see RUN\-OPTIONS below.
.LP
.RE
.LP
\f2<jnlp>\fP
.LP
.RS 3
.LP
.LP
This can be either the path of, or the Uniform Resource Locater (URL) of the JNLP (Java Network Launching Protocol) file.
.LP
.RE
.LP
\f2[control\-options]\fP
.LP
.RS 3
.LP
.LP
Command\-line control\-options. control\-options may be in any order. For a discussion of the various control\-options, see CONTROL\-OPTIONS below.
.LP
.RE
.RE
.SS
DESCRIPTION
.LP
.RS 3
.SH "DESCRIPTION"
.LP
.LP
The \f2javaws\fP command launches Java Web Start, which is the reference implementation of the Java Network Launching Protocol (JNLP). Java Web Start launches Java applications/applets hosted on a network.
...
...
@@ -103,256 +69,154 @@ If a JNLP file is specified, \f2javaws\fP will launch the Java application/apple
.LP
The \f2javaws\fP launcher has a set of options that are supported in the current release. However, the options may be removed in a future release.
.LP
.RE
.SS
RUN\-OPTIONS
.LP
.RS 3
.SH "RUN\-OPTIONS"
.LP
.LP
\f2\-offline\fP
.LP
.RS 3
.LP
.LP
run Java Web Start in offline mode.
Run Java Web Start in offline mode.
.LP
.RE
.LP
\f2\-Xnosplash\fP
.LP
.RS 3
.LP
.LP
disable the display of the initial splash screen.
Do not display the initial splash screen.
.LP
.RE
.LP
\f2\-open <arguments>\fP
.LP
.RS 3
.LP
.LP
If specified, replaces the arguments in the jnlp file with \f2\-open <arguments>\fP.
.LP
.RE
.LP
\f2\-print <arguments>\fP
.LP
.RS 3
.LP
.LP
If specified, replaces the arguments in the jnlp file with \f2\-print <arguments>\fP.
.LP
.RE
.LP
\f2\-online\fP
.LP
.RS 3
.LP
.LP
run in online mode (default behavior).
Use online mode (default behavior).
.LP
.RE
.LP
\f2\-wait\fP
.LP
.RS 3
.LP
.LP
If specified, the \f2javaws\fP process will not exit until the application exits.
If specified, the \f2javaws\fP process will not exit until the application exits. This option does not function as described on Windows platforms.
.LP
.RE
.LP
\f2\-verbose\fP
.LP
.RS 3
.LP
.LP
display additional output.
Display additional output.
.LP
.RE
.LP
\f2\-J<option>\fP
.LP
.RS 3
.LP
.LP
supply options to the vm.
Supply options to the VM.
.LP
.RE
.LP
\f2\-system\fP
.LP
.RS 3
.LP
Run the application from the system cache only.
.LP
run the application from the system cache only.
.SH "CONTROL\-OPTIONS"
.LP
.RE
.RE
.SS
CONTROL\-OPTIONS
.LP
.RS 3
\f2\-viewer\fP
.LP
.LP
\f2\-viewer\fP
Show the Cache Viewer in the Java Control Panel.
.LP
.RS 3
.LP
\f2\-clearcache\fP
.LP
show the Cache Viewer in the java control panel
.LP
.RE
Remove all non\-installed applications from the cache.
Options, if used, should follow immediately after the command name.
.br
.TP 3
connection = pid | host:port | jmxUrl
.RS 3
\f2pid\fP\ \ \ Process ID of a local Java VM. The Java VM must be running with the same user ID as the user ID running jconsole. See
.TP 2
o
\f2pid\fP Process ID of a local Java VM. The Java VM must be running with the same user ID as the user ID running jconsole. See
.na
\f2JMX Monitoring and Management\fP @
.fi
http://java.sun.com/javase/6/docs/technotes/guides/management/agent.html for details.
.br
\f2host\fP:\f2port\fP\ \ Name of the host system on which the Java VM is running and the port number specified by the system property \f2com.sun.management.jmxremote.port\fP when the Java VM was started. See
http://download.oracle.com/javase/7/docs/technotes/guides/management/agent.html for details.
.TP 2
o
\f2host\fP:\f2port\fP Name of the host system on which the Java VM is running and the port number specified by the system property \f2com.sun.management.jmxremote.port\fP when the Java VM was started. See
.na
\f2JMX Monitoring and Management\fP @
.fi
http://java.sun.com/javase/6/docs/technotes/guides/management/agent.html for details.
.br
\f2jmxUrl\fP\ \ Address of the JMX agent to be connected to as described in
http://download.oracle.com/javase/7/docs/technotes/guides/management/agent.html for details.
.TP 2
o
\f2jmxUrl\fP Address of the JMX agent to be connected to as described in
The \f3jconsole\fP command launches a graphical console tool that enables you to monitor and manage Java applications and virtual machines on a local or remote machine.
...
...
@@ -83,18 +80,16 @@ The \f3jconsole\fP command launches a graphical console tool that enables you to
On Windows, \f3jconsole\fP does not associate with a console window. It will, however, display a dialog box with error information if the \f3jconsole\fP command fails for some reason.
.LP
.SH "OPTIONS"
.LP
.LP
.RS 3
.TP 3
\-interval=n
Set the update interval to \f2n\fP seconds (default is 4 seconds).
.TP 3
\-notile\
\-notile
Do not tile windows initially (for two or more connections).
.TP 3
\-pluginpath\ plugins
\-pluginpath plugins
Specify a list of directories or JAR files which are searched for JConsole plugins. The \f2plugins\fP path should contain a provider\-configuration file named:
.br
.nf
...
...
@@ -104,20 +99,19 @@ Specify a list of directories or JAR files which are searched for JConsole plugi
.fl
\fP
.fi
.LP
containing one line for each plugin specifying the fully qualified class name of the class implementing the
." Copyright (c) 1995, 2010, Oracle and/or its affiliates. All rights reserved.
." Copyright (c) 1995, 2011, Oracle and/or its affiliates. All rights reserved.
." DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
."
." This code is free software; you can redistribute it and/or modify it
...
...
@@ -19,22 +19,16 @@
." or visit www.oracle.com if you need additional information or have any
." questions.
."
.TH jdb 1 "02 Jun 2010"
.TH jdb 1 "10 May 2011"
.LP
.SH "Name"
jdb \- The Java Debugger
.LP
.RS 3
.LP
.LP
\f3jdb\fP helps you find and fix bugs in Java language programs.
.LP
.RE
.SH "SYNOPSIS"
.LP
.LP
.nf
\f3
...
...
@@ -43,9 +37,6 @@ jdb \- The Java Debugger
.fl
.fi
.LP
.RS 3
.LP
.RS 3
.TP 3
...
...
@@ -60,23 +51,17 @@ Arguments passed to the \f2main()\fP method of \f2class\fP.
.RE
.LP
.RE
.SH "DESCRIPTION"
.LP
.LP
.LP
The Java Debugger, \f3jdb\fP, is a simple command\-line debugger for Java classes. It is a demonstration of the
.na
\f2Java Platform Debugger Architecture\fP @
.fi
http://java.sun.com/javase/6/docs/technotes/guides/jpda/index.html that provides inspection and debugging of a local or remote Java Virtual Machine.
http://download.oracle.com/javase/7/docs/technotes/guides/jpda/index.html that provides inspection and debugging of a local or remote Java Virtual Machine.
.LP
.SS
Starting a jdb Session
.LP
.RS 3
.LP
.LP
There are many ways to start a jdb session. The most frequently used way is to have \f3jdb\fP launch a new Java Virtual Machine (VM) with the main class of the application to be debugged. This is done by substituting the command \f3jdb\fP for \f3java\fP in the command line. For example, if your application's main class is MyClass, you use the following command to debug it under JDB:
...
...
@@ -137,7 +122,7 @@ There are many other ways to connect the debugger to a VM, and all of them are s
.na
\f2documentation\fP @
.fi
http://java.sun.com/javase/6/docs/technotes/guides/jpda/conninv.html on these connection options. For information on starting a J2SE 1.4.2 or early VM for use with \f3jdb\fP see the
http://download.oracle.com/javase/7/docs/technotes/guides/jpda/conninv.html on these connection options. For information on starting a J2SE 1.4.2 or early VM for use with \f3jdb\fP see the
.na
\f21.4.2 documentation\fP @
.fi
...
...
@@ -148,9 +133,6 @@ Basic jdb Commands
.LP
.LP
The following is a list of the basic \f3jdb\fP commands. The Java debugger supports other commands which you can list using \f3jdb\fP's \f2help\fP command.
.LP
.RS 3
.LP
.RS 3
.TP 3
...
...
@@ -165,9 +147,11 @@ Continues execution of the debugged application after a breakpoint, exception, o
.TP 3
print
Displays Java objects and primitive values. For variables or fields of primitive types, the actual value is printed. For objects, a short description is printed. See the \f2dump\fP command below for getting more information about an object.
.LP
.br
.br
\f2NOTE: To display local variables, the containing class must have been compiled with the \fP\f2javac(1)\fP\f2 \fP\f2\-g\fP option.
.LP
.br
.br
\f2print\fP supports many simple Java expressions including those with method invocations, for example:
.RS 3
.TP 2
...
...
@@ -189,14 +173,12 @@ o
.TP 3
dump
For primitive values, this command is identical to \f2print\fP. For objects, it prints the current value of each field defined in the object. Static and instance fields are included.
.LP
.br
.br
The \f2dump\fP command supports the same set of expressions as the \f2print\fP command.
.TP 3
threads
List the threads that are currently running. For each thread, its name and current status are printed, as well as an index that can be used for other commands, for example:
.RS 3
.LP
.nf
\f3
.fl
...
...
@@ -204,7 +186,6 @@ List the threads that are currently running. For each thread, its name and curre
.fl
\fP
.fi
.RE
In this example, the thread index is 4, the thread is an instance of java.lang.Thread, the thread name is "main", and it is currently running,
.TP 3
thread
...
...
@@ -212,17 +193,14 @@ Select a thread to be the current thread. Many \f3jdb\fP commands are based on t
.TP 3
where
\f2where\fP with no arguments dumps the stack of the current thread. \f2where all\fP dumps the stack of all threads in the current thread group. \f2where\fP \f2threadindex\fP dumps the stack of the specified thread.
.LP
.br
.br
If the current thread is suspended (either through an event such as a breakpoint or through the \f2suspend\fP command), local variables and fields can be displayed with the \f2print\fP and \f2dump\fP commands. The \f2up\fP and \f2down\fP commands select which stack frame is current.
.RE
.LP
.RE
.SS
Breakpoints
.LP
.RS 3
.LP
.LP
Breakpoints can be set in \f3jdb\fP at line numbers or at the first instruction of a method, for example:
...
...
@@ -249,22 +227,14 @@ If a method is overloaded, you must also specify its argument types so that the
.LP
The \f2clear\fP command removes breakpoints using a syntax as in "\f2clear\ MyClass:45\fP". Using the \f2clear\fP or command with no argument displays a list of all breakpoints currently set. The \f2cont\fP command continues execution.
.LP
.RE
.SS
Stepping
.LP
.RS 3
.LP
.LP
The \f2step\fP commands advances execution to the next line whether it is in the current stack frame or a called method. The \f2next\fP command advances execution to the next line in the current stack frame.
.LP
.RE
.SS
Exceptions
.LP
.RS 3
.LP
.LP
When an exception occurs for which there isn't a catch statement anywhere in the throwing thread's call stack, the VM normally prints an exception trace and exits. When running under \f3jdb\fP, however, control returns to \f3jdb\fP at the offending throw. You can then use \f3jdb\fP to diagnose the cause of the exception.
...
...
@@ -278,11 +248,7 @@ The \f2ignore\fP command negates the effect of a previous \f2catch\fP command.
.LP
\f2NOTE: The \fP\f2ignore\fP command does not cause the debugged VM to ignore specific exceptions, only the debugger.
.LP
.RE
.RE
.SH "Command Line Options"
.LP
.LP
.LP
When you use \f3jdb\fP in place of the Java application launcher on the command line, \f3jdb\fP accepts many of the same options as the java command, including \f2\-D\fP, \f2\-classpath\fP, and \f2\-X<option>\fP.
...
...
@@ -335,7 +301,7 @@ Other options are supported for alternate mechanisms for connecting the debugger
.na
\f2documentation\fP @
.fi
http://java.sun.com/javase/6/docs/technotes/guides/jpda/conninv.html on these connection alternatives.
http://download.oracle.com/javase/7/docs/technotes/guides/jpda/conninv.html on these connection alternatives.
.LP
.SS
Options Forwarded to Debuggee Process
...
...
@@ -357,8 +323,6 @@ Non\-standard target VM option
Options, if used, should follow immediately after the command name.
.br
.TP 3
heap\-dump\-file
Java binary heap dump file to be browsed. For a dump file that contains multiple heap dumps, you may specify which dump in the file by appending "#<number> to the file name, i.e. "foo.hprof#3".
.RE
.LP
.SH "DESCRIPTION"
.LP
.LP
...
...
@@ -69,7 +67,7 @@ Use jconsole(1) option to obtain a heap dump via
.na
\f2HotSpotDiagnosticMXBean\fP @
.fi
http://java.sun.com/javase/6/docs/jre/api/management/extension/com/sun/management/HotSpotDiagnosticMXBean.html at runtime;
http://download.oracle.com/javase/7/docs/jre/api/management/extension/com/sun/management/HotSpotDiagnosticMXBean.html at runtime;
.TP 2
o
Heap dump will be generated when OutOfMemoryError is thrown by specifying \-XX:+HeapDumpOnOutOfMemoryError VM option;
." Copyright (c) 2004, 2010, Oracle and/or its affiliates. All rights reserved.
." Copyright (c) 2004, 2011, Oracle and/or its affiliates. All rights reserved.
." DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
."
." This code is free software; you can redistribute it and/or modify it
...
...
@@ -19,15 +19,13 @@
." or visit www.oracle.com if you need additional information or have any
." questions.
."
.TH jinfo 1 "02 Jun 2010"
.TH jinfo 1 "10 May 2011"
.LP
.SH "Name"
jinfo \- Configuration Info
.LP
.SH "SYNOPSIS"
.LP
.LP
.nf
\f3
...
...
@@ -42,55 +40,56 @@ jinfo \- Configuration Info
.LP
.SH "PARAMETERS"
.LP
.LP
.RS 3
.TP 3
option
Options are mutually exclusive. Option, if used, should follow immediately after the command name.
.RE
.LP
.RS 3
.TP 3
pid
process id for which the configuration info is to be printed. The process must be a Java process. To get a list of Java processes running on a machine, jps(1) may be used.
.RE
.LP
.RS 3
.TP 3
executable
Java executable from which the core dump was produced.
.RE
.LP
.RS 3
.TP 3
core
core file for which the configuration info is to be printed.
.RE
.LP
.RS 3
.TP 3
remote\-hostname\-or\-IP
remote debug server's (see jsadebugd(1)) hostname or IP address.
.RE
.LP
.RS 3
.TP 3
server\-id
optional unique id, if multiple debug servers are running on the same remote host.
.RE
.RE
.LP
.SH "DESCRIPTION"
.LP
.LP
.LP
\f3jinfo\fP prints Java configuration information for a given Java process or core file or a remote debug server. Configuration information includes Java System properties and Java virtual machine command line flags. If the given process is running on a 64\-bit VM, you may need to specify the \f2\-J\-d64\fP option, e.g.:
.br
.LP
.RS 3
.LP
jinfo \-J\-d64 \-sysprops pid
.RE
.LP
.LP
\f3NOTE \- This utility is unsupported and may or may not be available in future versions of the JDK. In Windows Systems where dbgeng.dll is not present, 'Debugging Tools For Windows' need to be installed to have these tools working. Also, \fP\f4PATH\fP\f3 environment variable should contain the location of \fP\f4jvm.dll\fP\f3 used by the target process or the location from which the Crash Dump file was produced.\fP
.LP
...
...
@@ -98,8 +97,6 @@ jinfo \-J\-d64 \-sysprops pid
\f3For example, \fP\f4set PATH=<jdk>\\jre\\bin\\client;%PATH%\fP
." Copyright (c) 2004, 2010, Oracle and/or its affiliates. All rights reserved.
." Copyright (c) 2004, 2011, Oracle and/or its affiliates. All rights reserved.
." DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
."
." This code is free software; you can redistribute it and/or modify it
...
...
@@ -19,15 +19,13 @@
." or visit www.oracle.com if you need additional information or have any
." questions.
."
.TH jmap 1 "02 Jun 2010"
.TH jmap 1 "10 May 2011"
.LP
.SH "Name"
jmap \- Memory Map
.LP
.SH "SYNOPSIS"
.LP
.LP
.nf
\f3
...
...
@@ -42,8 +40,6 @@ jmap \- Memory Map
.LP
.SH "PARAMETERS"
.LP
.LP
.RS 3
.TP 3
...
...
@@ -73,14 +69,9 @@ optional unique id, if multiple debug servers are running on the same remote hos
.LP
.SH "DESCRIPTION"
.LP
.LP
.LP
\f3jmap\fP prints shared object memory maps or heap memory details of a given process or core file or a remote debug server. If the given process is running on a 64\-bit VM, you may need to specify the \f2\-J\-d64\fP option, e.g.:
.LP
.RS 3
.LP
.nf
\f3
...
...
@@ -89,10 +80,11 @@ jmap \-J\-d64 \-heap pid
.fl
\fP
.fi
.RE
.LP
\f3NOTE \- This utility is unsupported and may or may not be available in future versions of the JDK. In Windows Systems where dbgeng.dll is not present, 'Debugging Tools For Windows' needs to be installed to have these tools working. Also, \fP\f4PATH\fP\f3 environment variable should contain the location of \fP\f4jvm.dll\fP\f3 used by the target process or the location from which the Crash Dump file was produced.\fP
.LP
\f3NOTE: This utility is unsupported and may or may not be available in future versions of the JDK. In Windows Systems where dbgeng.dll is not present, 'Debugging Tools For Windows' needs to be installed to have these tools working. Also, \fP\f4PATH\fP\f3 environment variable should contain the location of \fP\f4jvm.dll\fP\f3 used by the target process or the location from which the Crash Dump file was produced.\fP
.LP
.LP
\f3For example, \fP\f4set PATH=<jdk>\\jre\\bin\\client;%PATH%\fP
.LP
...
...
@@ -100,13 +92,11 @@ jmap \-J\-d64 \-heap pid
.LP
.SH "OPTIONS"
.LP
.LP
.RS 3
.TP 3
<no option>
When no option is used \f3jmap\fP prints shared object mappings. For each shared object loaded in the target VM, start address, the size of the mapping, and the full path of the shared object file are printed. This is similar to the Solaris \f3pmap\fP utility.
When no option is used jmap prints shared object mappings. For each shared object loaded in the target VM, start address, the size of the mapping, and the full path of the shared object file are printed. This is similar to the Solaris \f3pmap\fP utility.
." Copyright (c) 2004, 2010, Oracle and/or its affiliates. All rights reserved.
." Copyright (c) 2004, 2011, Oracle and/or its affiliates. All rights reserved.
." DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
."
." This code is free software; you can redistribute it and/or modify it
...
...
@@ -19,15 +19,13 @@
." or visit www.oracle.com if you need additional information or have any
." questions.
."
.TH jps 1 "02 Jun 2010"
.TH jps 1 "10 May 2011"
.LP
.SH "Name"
jps \- Java Virtual Machine Process Status Tool
.LP
.SH "SYNOPSIS"
.LP
.LP
.nf
\f3
...
...
@@ -40,8 +38,6 @@ jps \- Java Virtual Machine Process Status Tool
.LP
.SH "PARAMETERS"
.LP
.LP
.RS 3
.TP 3
...
...
@@ -54,8 +50,6 @@ The host identifier of the host for which the process report should be generated
.LP
.SH "DESCRIPTION"
.LP
.LP
.LP
The \f3jps\fP tool lists the instrumented HotSpot Java Virtual Machines (JVMs) on the target system. The tool is limited to reporting information on JVMs for which it has the access permissions.
...
...
@@ -76,8 +70,6 @@ The list of JVMs produced by the \f3jps\fP command may be limited by the permiss
\f3NOTE:\fP This utility is unsupported and may not be available in future versions of the JDK. It is not currently available on Windows 98 and Windows ME platforms.
.LP
.SH "OPTIONS"
.LP
.LP
.LP
The \f3jps\fP command supports a number of options that modify the output of the command. These options are subject to change or removal in the future.
...
...
@@ -106,9 +98,6 @@ Pass \f2option\fP to the \f3java\fP launcher called by \f3jps\fP. For example, \
.LP
.SS
HOST IDENTIFIER
.LP
.RS 3
.LP
.LP
The host identifier, or \f2hostid\fP is a string that indicates the target system. The syntax of the \f2hostid\fP string largely corresponds to the syntax of a URI:
...
...
@@ -140,10 +129,7 @@ The treatment of this parameter depends on the implementation. For the optimized
.RE
.LP
.RE
.SH "OUTPUT FORMAT"
.LP
.LP
.LP
The output of the \f3jps\fP command follows the following pattern:
...
...
@@ -168,8 +154,6 @@ Where all output tokens are separated by white space. An \f2arg\fP that includes
.LP
.SH "EXAMPLES"
.LP
.LP
.LP
This section provides examples of the \f3jps\fP command.
