Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

launch4j 3.0.1 (Stable branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News launch4j 3.0.1 (Stable branch)
# 1  
Old 08-04-2008
launch4j 3.0.1 (Stable branch)
Image Launch4j is a cross-platform tool for wrapping Java applications distributed as jars in Windows native executables. The executable can be configured to search for a certain JRE version or use a bundled one, and it's possible to set runtime options, like the initial/max heap size. The wrapper also provides better user experience through an application icon, a native pre-JRE splash screen, a custom process name, and a Java download page in case the appropriate JRE cannot be found. The increase in size of the application is small. License: BSD License (revised) Changes:
Support for 64-bit Windows, 64-bit JRE, and IBM JRE was added. A Java runtime preference option was introduced. It is now possible to set the initial process priority and allow running only a single instance of the application. Dynamic initial and maximum heap sizes were added. The error reporting was redesigned and now supports custom messages. The runtime logging produces more detailed output. Various bugs were fixed, and the license was changed to a less restrictive one.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT MOJAVE

jsadebugd

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)