Download List

Descripción del Proyecto

The Java Service Wrapper line of products are highly configurable tools which not only allow Java applications to be installed and controlled like native Windows Services or UNIX daemon processes, but also include advanced fault detection software which monitors an application. The Java Service Wrapper is able to detect crashes, freezes, out of memory and other exception events, then notify you via email when there is a problem. It does not stop there however, the Java Service Wrapper is unique in its ability to automatically react to any of the above events by shutting down your application or restarting it with a minimum of delay. These features combine to help you guarantee the maximum possible uptime for your application or service. The Wrapper allows businesses and developers to rapidly deploy reliable Java based solutions on a wide variety of platforms in a consistent way.

For more information about our Standard and Professional edition versions, please visit the Java Service Wrapper site.

System Requirements

System requirement is not defined
Wrapper
Wrapper バージョン 3.5.1
Wrapperソース
Wrapperプリリリース

Publicado: 2010-07-08 12:00
Wrapper Wrapper バージョン 3.5.1 (24 files Ocultar)

Release Notes

Version 3.5.1: Changes and bug fixes

  • Start using a system function to determine whether or not a character in the configuration file is a control character or not. This way it works on non-ASCII platforms.

  • (Standard / Professional Edition)

    Fix a crash on Windows platforms caused by freeing up unallocated memory while loading the Wrapper's configuration.

  • Add debug output describing the system and current code pages on Windows versions to help understand encoding and mojibake issues.

  • Add a Japanese localized src/conf/wrapper.conf.in_ja template configuration file to assist Japanese users. See the Example configuration.

  • Fix an potential deadlock on UNIX platforms if the JVM exits while logging is taking place and the wrapper.debug or undocumented wrapper.state_output properties were set to TRUE.

  • (Standard / Professional Edition)

    Rework the way text is localized so that mallocs are all handled on initialization. 3.5.0 had problems with occassional freezes and crashes caused by mallocs being made within signal handlers. The problems were rare unless debug output was enabled.

  • Greatly simplify signal handlers on all platforms so they now do as little as possible, actions are now queued and then processed by the main thread.

  • (Standard / Professional Edition)

    Fix a problem where the hostname in the wrapper.syslog.remote.host couldn't resolve a hostname (IP Address was working).

  • (Standard / Professional Edition)

    Add debug output on Windows versions to help debug localization and code page issues.

  • (Standard / Professional Edition)

    Fix a localization problem on Windows where the Wrapper was using the system-wide language rather than that of the current process. This was resulting in mojibake if the Wrapper was launched in a new console if that new console did not support the required code page. This was only an issue if the user had changed the active code page from the default for their Windows desktop.

  • Fix a problem on Windows platforms where the JVM child output was being logged with an extra line feed in some cases.

  • Fix a problem running the DemoApp from some Network shares on Windows.

  • Add a new WrapperManager.isWindows() and WrapperManager.isMacOSX() methods to make it easy to write such conditional code as both platforms can require non standard code.

  • (Standard / Professional Edition)

    Make the GetHostId.bat file more robust so it can be executed using a relative reference from the command line. It also now supports Delta-pack style Wrapper binary naming and falling back to use which binaries are available.

  • Change the timing of when the wrapper.working.dir is set so that any error messages generated while loading the configuration will be logged to the correct log file. It is also needed for Standard and Professional Editions to ensure that the language pack is loaded from the correct location so that all such messages will be in the correct locale.

  • Fix a problem on UNIX platforms where the status command was failing with an error due to the localization feature added in 3.5.0.

Changelog

No Changelogs