jsadebugd(1) [mojave man page]

jsadebugd(1)						      General Commands Manual						      jsadebugd(1)

NAME

       jsadebugd - serviceability agent debug daemon

SYNOPSIS

       jsadebugd [pid] [server-id]
       jsadebugd executable core [server-id]

DESCRIPTION

       jsadebugd  attaches to a Java process or core file and acts as a debug server. Remote clients such as jstack, jmap, and jinfo can attach to
       the server using Java Remote Method Invocation (RMI). Before starting jsadebugd, rmiregistry must be started with:

	      rmiregistry -J-Xbootclasspath/p:$JAVA_HOME/lib/sajdi.jar

       where $JAVA_HOME is the J2SE SDK installation directory.  If rmiregistry was not started, jsadebugd will start an rmiregistry in a standard
       (1099) port internally. Debug server may be stopped by sending SIGINT (pressing Ctrl-C) to it.

       NOTE - This utility is unsupported and may or may not be available in future versions of the J2SE SDK.  jinfo is not currently available on
       Windows platforms or on the Linux Itanium platform.

PARAMETERS

       pid	      process id of the process to which the debug server should attach. The process must be a Java process. To get a list of Java
		      processes  running  on  a  machine,  jps	may be used.  At most one instance of the debug server may be attached to a single
		      process.

       executable     Java executable from which the core dump was produced.

       core	      core file to which the debug server should attach.

       server-id      optional unique id, needed if multiple debug servers are started on the same machine. This ID must be used by remote clients
		      to identify the particular debug server to attach. Within a single machine, this ID must be unique.

SEE ALSO

       jinfo(1) jmap(1) jps(1) jstack(1) rmiregistry(1)

								   13 June 2004 						      jsadebugd(1)

rmiregistry(1)						      General Commands Manual						    rmiregistry(1)

NAME

       rmiregistry - Java remote object registry

SYNOPSIS

       rmiregistry [ port ]

DESCRIPTION

       The  rmiregistry command creates and starts a remote object registry on the specified port on the current host.	If port number is omitted,
       the registry is started on port 1099.  The rmiregistry command produces no output and is typically run in the background.  For example:

	      example% rmiregistry &

       A remote object registry is a bootstrap naming service that is used by RMI servers on a host to bind remote objects to names.  Clients  can
       then look up remote objects and make remote method invocations.

       The registry is typically used to locate the first remote object on which an application needs to invoke methods.  That object in turn pro-
       vides application-specific support for finding other objects.

       The methods of the java.rmi.registry.LocateRegistry class are used to get a registry operating on a particular host or host and port.

       The URL-based methods of the java.rmi.Naming class operate on a registry and can be used to look up a remote object, bind a simple (string)
       name to a remote object, rebind a new name to a remote object (overriding the old binding), unbind a remote object, and list the URLs bound
       in the registry.

OPTIONS

       The following option is supported:

       -Joption       Used in conjunction with any java option, this option passes option (no spaces between -J and option) on to the java  inter-
		      preter.

SEE ALSO

       See (or search java.sun.com) for the following:

       java.rmi.Naming @
	    http://java.sun.com/j2se/1.5/docs/api/java/rmi/Naming.html

       java.rmi.registry.LocateRegistry @
	    http://java.sun.com/j2se/1.5/docs/api/java/rmi/registry/LocateRegistry.html

								    23 Apr 2001 						    rmiregistry(1)