Java Service Wrapper Standard Edition 3.5.13 Testing

Java Service Wrapper Standard Edition 3.5.13 Testing  is described as a handy, smart and effective program which enables a Java Application to be run as a Windows Service or Unix Daemon.

It also monitors the health of your Application and JVM.

Benefits:

• There is no need for additional programing in your application to integrate it with product.
• Automatic customizable response when something happens in your application or JVM.
• Notifications when there is a problem in need of attention.
• Support better your customers thanks to logging features
• You can schedule events in a standard way in various platforms..
• Deploy and install your applications as a Windows Service or Unix daemon in various platforms.

Major Features:

1. Ability to run as a Windows Service
2. Ability to run as a UNIX daemon
3. Codeless Integration
4. Capture and logging of all console output from JVM
5. Flexible classpath configuration, including wildcards
6. Custom working directory
7. JVM Monitoring and restart functionality
8. Single instance enforcement
9. Ability to control process priority
10. Triggered JVM shutdowns, restarts, and thread dumps
11. Fully localized Wrapper
12. Ability to localize user applications
13. Automatic Java thread deadlock detection and response
14. Setup Windows mapped drives when running as a service
15. Ability to log to a remote syslog server from all platforms
16. Relative Memory Limits
17. Consoleless Binary (Windows)
18. Customizable Icon (Windows)
19. Customizable Splash Screen (Windows)
20. Control the timezone used for events and log output
21. Configure Service Recovery (Windows)

Enhancements:

• Fix a typo in the script where the environment variable 'TR_BIN' should actually be 'TREXE'. This was causing the "install" command on UNIX platforms to fail. Introduced in 3.5.12.
• Fix a heap corruption which could lead to a crash that would occur the second time an internal buffer used for logging was expanded. The buffer would be expanded the first time a log line over 2048 characters in length was encountered. Then the second expansion would happen when a line at least 1024 characters longer was encountered. Introduced in 3.5.11. Bug #3423108.

Requirements:

• Java