Oracle Java Web Start Launcher Download
Sam Eich
The Java runtime searches for the startup class, and other classesused, in three sets of locations: the bootstrap class path, theinstalled extensions, and the user class path.Non-option arguments after the class name or JAR file name are passedto the main function.The javaw command is identical to java, except that with javaw there is no associated console window. Use javaw when you don't want a command prompt window to appear. The javaw launcher will, however, display a dialog box with error information if a launch fails for some reason.OPTIONSThe 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 default Java HotSpot VMs provide a set of non-standard options. The non-standard options are subject to change in future releases. Standard Options -client Select the Java HotSpot Client VM. This is the default. -server Select the Java HotSpot Server VM. -classpath classpath -cp classpathSpecify a list of directories, JAR archives, and ZIParchives to search for class files. Class path entries areseparated by semicolons (;). Specifying-classpath or -cp overrides any setting of theCLASSPATH environment variable.If -classpath and -cp are not used andCLASSPATH is not set, the user class path consists ofthe current directory (.).For more information on class paths, see Setting the Class Path. -Dproperty=valueSet a system property value. If value is a string that contains spaces, you must enclose the string in double quotes: java -Dfoo="some string" SomeClass -enableassertions[:"..." : ]-ea[:"..." : ]Enable assertions. Assertions are disabled by default. With no arguments, enableassertions or -ea enables assertions. With oneargument ending in "...", the switch enables assertions in thespecified package and any subpackages. If the argument is simply"...", the switch enables assertions in the unnamed package in the currentworking directory. With one argument not ending in "...", the switchenables assertions in the specified class.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 com.wombat.fruitbat (and any subpackages), the followingcommand could be used:java -ea:com.wombat.fruitbat... The -enableassertions and -ea switches apply to all s 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 not apply to system.This makes it easy to turn on asserts in all classes except for systemclasses. A separate switch is provided to enable asserts in all systemclasses; see -enablesystemassertions below.-disableassertions[:"..." :The -disableassertions and -da switches apply to all ss 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 not apply to system.This makes it easy to turn on asserts in all classes except for systemclasses. A separate switch is provided to enable asserts in all systemclasses; see -disablesystemassertions below.-enablesystemassertions-esaEnable asserts in all system classes (sets the default assertion status for system classes to true).-disablesystemassertions-dsaDisables asserts in all system classes. -jarExecute a program encapsulated in a JAR file. The firstargument is the name of a JAR file instead of a startupclass name. In order for this option to work, the manifest of the JAR file must contain a line of the form Main-Class: classname. Here, classname identifies the class having the public static void main(String[] args) method that serves as your application's starting point. See the Jar tool reference page and the Jar trail of the Java Tutorial for information about working with Jar files and Jar-file manifests. When you use this option, the JAR file is the source of all user classes, and other user class path settings are ignored. -verbose -verbose:classDisplay information about each class loaded. -verbose:gcReport on each garbage collection event. -verbose:jniReport information about use of native methods and otherJava Native Interface activity. -versionDisplay version information and exit. -showversionDisplay version information and continue. -? -helpDisplay usage information and exit. -XDisplay information about non-standard options and exit.Non-Standard Options -Xint Operate in interpreted-only mode. Compilation to native code is disabled, and all bytecodes are executed by the interpreter. The performance benefits offered by the Java HotSpot Client VM's adaptive compiler will not be present in this mode. -Xbatch Disable background compilation. Normally the VM will compile the method as a background task, running the method in interpreter mode until the background compilation is finished. The -Xbatch flag disables background compilation so that compilation of all methods proceeds as a foreground task until completed. -Xdebug Start with the debugger enabled. Refer to jdb description for more details and an example. -Xbootclasspath:bootclasspathSpecify a semicolon-separated list of directories, JARarchives, and ZIP archives to search for boot class files.These are used in place of the boot class files included in theJava 2 SDK. Note: Applications that use this option for the purpose of overriding a class in rt.jar should not be deployed as doing so would contravene the Java 2 Runtime Environment binary code license. -Xbootclasspath/a:path Specify a semicolon-separated path of directires, JAR archives, and ZIP archives to append to the default bootstrap class path. -Xbootclasspath/p:path Specify a semicolon-separated path of directires, JAR archives, and ZIP archives to prepend in front of the default bootstrap class path. Note: Applications that use this option for the purpose of overriding a class in rt.jar should not be deployed as doing so would contravene the Java 2 Runtime Environment binary code license. -Xcheck:jni Perform additional checks for Java Native Interface (JNI) functions. Specifically, the Java Virtual Machine validates the parameters passed to the JNI function as well as the runtime environment data before processing the JNI request. Any invalid data encountered indicates a problem in the native code, and the Java Virtual Machine will terminate with a fatal error in such cases. Expect a performance degradation when this option is used. -Xfuture Perform strict class-file format checks. For purposes of backwards compatibility, the default format checks performed by the Java 2 SDK's virtual machine are no stricter than the checks performed by 1.1.x versions of the JDK software. The -Xfuture flag turns on stricter class-file format checks that enforce closer conformance to the class-file format specification. Developers are encouraged to use this flag when developing new code because the stricter checks will become the default in future releases of the Java application launcher. -XnoclassgcDisable class garbage collection. -Xincgc Enable the incremental garbage collector. The incremental garbage collector, which is off by default, will eliminate occasional garbage-collection pauses during program execution. However, it can lead to a roughly 10% decrease in overall GC performance.-Xloggc:file Report on each garbage collection event, as with -verbose:gc, but log this data to file. In addition to the information -verbose:gc gives, each reported event will be preceeded by the time (in seconds) since the first garbage-collection event. 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 -verbose:gc if both are given on the command line. -XmsnSpecify the initial size, in bytes, of the memory allocation pool. This value must be a multiple of 1024 greater than 1MB. Append the letter k or K to indicate kilobytes, or m or M to indicate megabytes. The default value is 2MB. Examples: -Xms6291456 -Xms6144k -Xms6m -Xmxn Specify the maximum size, in bytes, of the memory allocation pool. This value must a multiple of 1024 greater than 2MB. Append the letter k or K to indicate kilobytes, or m or M to indicate megabytes. The default value is 64MB. Examples: -Xmx83886080 -Xmx81920k -Xmx80m -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 be used in production systems. -Xrunhprof[:help][:=,...]Enables cpu, heap, or monitor profiling. This option is typically followed by a list of comma-separated "=
You should clear the java cache for your current 8.x install (be sure you select/check ALL THREE boxes in the "Delete Files and Applications" screen). You should delete any downloaded copies of admin.jnlp or start.jnlp and download a fresh copy from the UDI site. I'm not sure if there's actually anything in the cache directory you mention above, but if it's 6.0 you should probably delete anything in there also.
760c119bf3