|
From: Leif M. <le...@ta...> - 2003-03-02 10:25:01
|
Sorry for the long wait, but Version 3.0.0 has finally been released. The rework of the documentation took more time than I had planned. It is still a work in progress, but it was past time to get this version out. Please download this new version and let me know of any problems in the documentation or otherwise. I tried to add more descriptive tutorials of the integration process. As most of you have experience with integrating the Wrapper, I would be interested in any feedback on whether or not these tutorials will help simplify the process for new users. There were a lot of changes in this version, so be sure to take a look at the release notes for a full list of changes: http://wrapper.tanukisoftware.org/doc/english/release-notes.html Cheers, Leif Java Service Wrapper Revision History. -------------------------------------- 3.0.0 * Deprecated the com.silveregg.wrapper package in favor of org.tanukisoftware.wrapper. The classes and interfaces in the silveregg package will continue to function, but migration to the new package should be done when possible. See the project history for details. * On Windows systems change any forward slashes in the wrapper.java.command property to back slashes. Some users had reported having problems on Windows XP. * Implemented feature request #633178. Added WrapperManager.requestThreadDump() to force the current JVM to immediately perform a thread dump. * Fixed bug where wrapper.logfile.maxsize was being set to 0 if the 'k' or 'm' unit was ommitted. * Add the ability to specify an account name and password when installing an NT service. * Add a property, wrapper.ntservice.interactive, which makes it possible to control whether or not the Java process can gain access to the desktop while it is running as an NT service. * Add limited support for 1.2.x versions of Java. Shutdown hooks are supported until Java 1.3 so those functions will be disabled. If the application displays a GUI then Java 1.3 should be used as the GUI can not currently be displayed when using Java 1.2.x. * Made it possible to use the wrapper.pidfile property on all *nix platforms. Please notice that the property has been removed from the default wrapper.conf file. The property is not needed when the wrapper is launched with the bash shell script. The sh shell script will set the wrapper.pidfile when the wrapper is launched. If either of the scripts provided with the Wrapper distribution are used then the wrapper.pidfile should always be removed from your wrapper.conf file. * Added a new wrapper.daemonize property which, when set, will form the wrapper process to be a detached non-session group leader. This makes it possible to launch the wrapper in such a way that it will not be terminated when the user launching the process logs out. This had been a problem on Solaris systems when using the sh shell. The default sh and bash scripts both make use of this in the default. Please update your scripts for use with this version. Thanks to Rajiv Subrahmanyam for the patch. * Fix a problem where the Wrapper was incorrectly counting the number of non-daemon threads in BEA's JRockit Virtual Machine. This was causing the application to shutdown when the non-daemon thread count dropped to 1. * Added support for building the wrapper on AIX and HPUX systems. Thanks for the patches involved go out to Ashish Gawarikar and William Lee. * Implement feature request #653131 to force the JVM to immediately exit when the user presses CTRL-C multiple times. * Added a 'console' action to the bash and sh scripts to make it possible to launch the Wrapper in the current shell process. The 'start' task will launch the Wrapper as a spawned daemon process. * Fixed a problem where missing environment variables specified in classpath or library path properties were not being handled correctly. * Implemented feature request #676599 to enable the filtering of JVM output to trigger JVM restarts or Wrapper shutdowns. See the new wrapper.filter.trigger.n and wrapper.filter.action.n properties. * Modify the Win32 version of the Wrapper so that Environment Variables are always read from the system registry when the Wrapper is run as a service. By doing this, it makes it possible to change or add the system environment variables and have them take effect without having to first reboot the machine. * Implemented cascading configuration files. * Changed the default value for the wrapper.java.initmemory property to be 3Mb. The default on Windows and Linux JVMs is 2Mb, but the Solaris JVM requires a minimum of 3Mb. The minimum value accepted by the Wrapper was changed from 8Mb to 1Mb to make it possible to reduce the footprint of applications to what is possible without using the wrapper. * Improve the parsing of config files so that leading and trailing white space is now correctly trimmed. It is also now possible to have comments at the end of a line containing a property. * Modify the way exceptions thrown by an application's main method are presented to the user by the WrapperSimpleApp and WrapperStartStopApp so they no longer look like a problem with Wrapper configuration. |