JavaParty Logo

JavaParty

A distributed companion to Java
Current release 1.9.5

Bernhard Haumacher, Thomas Moschny and Michael Philippsen

Contents
General
 Features
 Requirements
 DownloadNew!
 Mailing ListsNew!
 Setup
 Quick Tour
displayed pageCommand Reference
 API
Language
 Syntax
 Object Model
 Transparent Threads
 Distributed ThreadsCool!
 RMACool!
 Synchronization
 Object Location
 Migration
 Remote Threads
 Replicated ObjectsCool!
 Multi-Application
Tuning
 Debugging
 uka.transport
 KaRMICool!
 KaRMI API
 Myrinet/GM
 OpenPBS
Examples
 Hello JavaParty
 ObjectModel
 BenchmarksNew!
Other info
 Papers
 Trouble Shooting
 History


See also
 CJ
 Generic Java


Powered by
Apache Ant
SourceForge
Subversion

JavaParty Reference

The JavaParty Compiler

The JavaParty compiler is derived from the Generic Java compiler and therefore accepts the same options plus some JavaParty specific options. The JavaParty compiler is invoked with the following command line:

jpc options* source-file.java+

You can specify options as described below followed by a list of Java or JavaParty source files.

-d output-directory

Specifies the output directory for compiled class files. You must specify this option when compiling classes that reside inside a package.

-classpath application-class-path

Path for loading classes referenced from source files being compiled. Alternatively, you can set the CLASSPATH environment variable.

-stubdebug

The JavaParty compiler automatically generates stubs and skeletons for remote classes. If you use KaRMI, the compiler generates debugging code that traces remote method calls via debugging messages.

-help

Prints all supported options.

Unix only: Invite a Java party

jpinvite [-cp|-classpath <application-class-path>]
         [-D<property-name>=<value>]*
         [-X<virtual-machine-option>]*
         [-J <argument-passed-directly-to-Java>]*
         [-nodenames <comma-separated-list-of-hosts>
         |-nodefile <PBS-style-node-file>]?
         [-frontend]?
         [-purify]?
         <class-name> <class-arguments>*

JPInvite spawns a Java virtual machine on all specified hosts, invokes your application class and shuts down the environment after the main() method returns.

The Java specific options are passed to each participating virtual machine. The script assumes that either the cluster has a common network file system, or the file system layout of each node is identical to the layout on the invoking machine.

-cp <application-class-path>
-classpath <application-class-path>
Set the class path for the application consistent on all participating virtual machines. Assumes, all computing nodes have a common network file system or have at least the same directory layout.
-D<property-name>=<value>
Set a system property consistent on all participating virtual machines.
-X<virtual-machine-option>
Set a non-standard option on the Java virtual machine.
-J <argument-passed-directly-to-Java>
Pass some other option directly to the underlying Java virtual machine.
-frontend

Use an extra front-end virtual machine for invoking a local main class. This front-end virtual machine does not become part of the dirstributed environment and can be used to start a local GUI.

To get X11 forwarding, for all your nodes, set the JPQ_RSH environment variable accordingly.

-purify
Purify the console output of the virtual machines spawning the distributed environment. This option prevents that lines of output from different virtual machines are merged. Additionaly, each line of output is prefixed with the number of the virtual machine that printed it. With this option, all output is redirected to standard output.

For the complete list of options please try:

jpinvite -help

Windows only: The JavaParty Runtime Manager

The runtime manager is the central instance in a JavaParty environment. It keeps track of registered virtual machines and manages information about loaded remote classes.

jprm option*

Starts the JavaParty runtime manager on the current machine.

-code runtime-manager-access-code

The JavaParty virtual machines use multi-cast to look up an active JavaParty environment for registration. Each JavaParty environment must use an unique code to make sure that a virtual machine registers at the right manager.

If no code is specified, your user name is used as default value. Therefore, only need to choose another code, if you want to start more than one JavaParty environment.

-port runtime-manager-port

Chooses an alternate port for exporting the registry (for details consult the RMI specification). You only need to use this option, if you want to start more than one runtime manger on the same host, or if the default port is use from another application.

Note: If you are using JavaParty for KaRMI, you also have to adapt the KaRMI configuration (see the KaRMI).

-verbose

Show what the runtime manager is doing.

-debug

Show information about remote classes loading.

Windows only: The JavaParty Virtual Machine

jpvm option*

Start one node of the distributed environment. The execution of a JavaParty program takes place in one ore more virtual machines.

-code runtime-manager-access-code

See the runtime manager.

-host runtime-manager-host

Only register the virtual machine on a runtime manager running on the specified host. By default the runtime manager is looked up using multi-cast.

-port runtime-manager-port

See the runtime manager.

If you specify the -host and -port options, no multi-cast is used.

Windows only: Application startup

jp jp-args* class-name arguments*

Invokes the applications main class. See JavaParty virtual machine for options accepted for choosing the runtime manager. The command returns when the main method of the application is completed.


For comments and bug reports please use the JavaParty users mailing list.
Page design & maintenance: Bernhard Haumacher.
Last update: Fri Mar 30 18:46:00 GMT+01:00 2007
Java is a trademark of Sun Microsystems.