Java Service Wrapper Example

  1. Java Exe Wrapper
  2. Java Service Wrapper Examples

Codota search - find any Java class or method. Java Wrapper Classes Tutorial with Examples October 30, 2015 admin This tutorial explains the concepts of Java wrapper classes with examples, shows how to convert from wrapper types to primitives and vice-a-versa, explains numeric wrapper classes and wraps up with character & boolean wrapper classes Character.

  • Licensing Overview
ExamplesLicensing Overview

Java Exe Wrapper

The Java Service Wrapper is being put to use by a wide range of users for a wide range of projects. This includes corporate and government infrastructure projects, commercial products and systems, and open source projects.

The Java Service Wrapper is available under any one of three licenses making it possible to choose to license most appropriate for a given project.

The full text of each license can be viewed by clicking on the license name.

  • Server License Agreement:

    This License Agreement allows you to use the Java Service Wrapper on a single physical or virtual server or workstation. Videoshidden hills stable. One license allows for the generation of a single License Key, which will authorize the Java Service Wrapper to be run on a single machine. Multiple instances of the Wrapper can be run for different applications on a single physical or virtual machine.

  • Development License Agreement:

    This License Agreement allows you to bundle and redistribute the Java Service Wrapper with one or more proprietary commercial applications without requiring that the source of the application be disclosed in any way. A single Development License allows your organization to generate multiple License Keys for applications which your organization develops and distributes. Each generated License Key is tied to a specific application without any restrictions on how many machines it is installed and run on. This type of license is also referred to as an OEM license by some customers.

  • Community License Agreement:

    This license agreement is based on the popular GPL v2 (General Public License ver.2) license used by many open source projects. For open source projects, this is a good choice as it allows the Wrapper to be redistributed as part of any application provided that all source of the application is made available to the user base free of charge.

If you are unsure which license is appropriate for your particular project, please read over the following examples.

  • Q: I am a member of a team developing a popular open source project which may or may not be used in commercial situations.

    A: The Community License Agreement will work fine in most cases as long as the entire application and all of its components are redistributed in such a way that the users of your solution can easily obtain the full source of the entire application.

  • Q: I would like to redistribute the Wrapper with our proprietary application to customers.

    A: The Development License Agreement will allow you to redistribute the Wrapper with your application without any restrictions on how you sell the resulting package.

  • Q: I would like to redistribute a modified version of the Wrapper with our proprietary application to customers.

    A: Currently only the Community Edition source is being made available for modification. If it is at all possible, we encourage you to contribute a patch to the Wrapper-User Mailing List where it will be discussed. If it fits the goals of the product suite, it will be included for all users to make use of.

    In cases where submitting a patch is NOT possible, the Development License Agreement will allow you to redistribute the modified copy of the Wrapper with your application without any restrictions on how you sell the resulting package.

Java Service Wrapper Examples

I have done this on other servers with allegedly the same configuration previously without issue, however on this particular server whenever I try and start the service it fails instantly with Error 1053 - which implies a timeout problem, however it happens so quickly (<1 second) that I’m doubtful that this is the root cause.
I have update my application to the latest x86.3.5.24 version and I get the same problem.
When I run the application on the console via a batch file it works fine.
The java installed is the 32 bit version :-
java version '1.7.0_45'
Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
Java HotSpot(TM) Client VM (build 24.45-b08, mixed mode, sharing)
When the program fails to start as a service there don’t seem to be any log files created at all. When I start the application as a batch / console application I get normal log files - which is reassuring but don’t contain anything helpful.
I have run the application as a service, with and without a domain user account. When I’ve used the domain account then that account is in the local Administrators group of the local server.
The windows event log does not show Error 1053, but it does log 2 errors each time I run my application which are :-
7000 - The service did not respond to the start or control request in a timely fashion.
7009 - A timeout was reached (60000 milliseconds) while waiting for the Commander4j Interface Wisbech Production service to connect.
The timeout value in 7009 above is set very high and as I’ve mentioned the application fails immediately when I try and start it.
At this point in time I’m out of ideas regarding how to diagnose the problem further.
Are there any windows requirements for the wrapper.exe to run - could it be that it does not have permissions to load a .dll when running as a service ?
PS. My config file is below.
# Configuration files must begin with a line specifying the encoding
# of the the file.
# Wrapper License Properties (Ignored by Community Edition)
# Professional and Standard Editions of the Wrapper require a valid
# License Key to start. Licenses can be purchased or a trial license
# requested on the following pages:
# http://wrapper.tanukisoftware.com/purchase
# http://wrapper.tanukisoftware.com/trial
# Include file problems can be debugged by removing the first '#'
# from the following line:
# The Wrapper will look for either of the following optional files for a
# valid License Key. License Key properties can optionally be included
# directly in this configuration file.
#include ./conf/wrapper-license.conf
#include ./conf/wrapper-license-%WRAPPER_HOST_NAME%.conf
# The following property will output information about which License Key(s)
# are being found, and can aid in resolving any licensing problems.
# Wrapper Localization
# Specify the locale which the Wrapper should use. By default the system
# locale is used.
#wrapper.lang=en_US # en_US or ja_JP
# Specify the location of the Wrapper's language resources. If these are
# missing, the Wrapper will default to the en_US locale.
# Wrapper Java Properties
# Java Application
# Locate the java binary on the system PATH:
# Specify a specific java binary:
# Tell the Wrapper to log the full generated Java command line.
# Java Main class. This class must implement the WrapperListener interface
# or guarantee that the WrapperManager class is initialized. Helper
# classes are provided to do this for you. See the Integration section
# of the documentation for details.
# Java Classpath (include wrapper.jar) Add class path elements as
# needed starting from 1
# Java Library Path (location of Wrapper.DLL or libwrapper.so)
# Java Bits. On applicable platforms, tells the JVM to run in 32 or 64-bit mode.
# Java Additional Parameters
# Initial Java Heap Size (in MB)
# Maximum Java Heap Size (in MB)
# Application parameters. Add parameters as needed starting from 1
# Wrapper Logging Properties
# Enables Debug output from the Wrapper.
# wrapper.debug=TRUE
# Format of output for the console. (See docs for formats)
# Log Level for console output. (See docs for log levels)
# Log file to use for wrapper output logging.
# Format of output for the log file. (See docs for formats)
# Log Level for log file output. (See docs for log levels)
# Maximum size that the log file will be allowed to grow to before
# the log is rolled. Size is specified in bytes. The default value
# of 0, disables log rolling. May abbreviate with the 'k' (kb) or
# 'm' (mb) suffix. For example: 10m = 10 megabytes.
# Maximum number of rolled log files which will be allowed before old
# files are deleted. The default value of 0 implies no limit.
# Log Level for sys/event log output. (See docs for log levels)
# Wrapper General Properties
# Allow for the use of non-contiguous numbered properties
# Do not start if the pid file already exists.
# Title to use when running as a console
# Wrapper JVM Checks
# Detect DeadLocked Threads in the JVM. (Requires Standard Edition)
# Out Of Memory detection.
# (Ignore output from dumping the configuration to the console. This is only needed by the TestWrapper sample application.)
# Ignore -verbose:class output to avoid false positives.
wrapper.filter.trigger.1000=[Loaded java.lang.OutOfMemoryError
# (Simple match)
# (Only match text in stack traces if -XX:+PrintClassHistogram is being used.)
#wrapper.filter.trigger.1001=Exception in thread '*' java.lang.OutOfMemoryError
wrapper.filter.message.1001=The JVM has run out of memory.
# Wrapper Email Notifications. (Requires Professional Edition)
# Common Event Email settings.
#wrapper.event.default.email.subject=[%WRAPPER_HOSTNAME%:%WRAPPER_NAME%:%WRAPPER_EVENT_NAME%] Event Notification
#wrapper.event.default.email.sender=<Sender email>
#wrapper.event.default.email.recipient=<Recipient email>
# Configure the log attached to event emails.
# Enable specific event emails.
# Specify custom mail content
wrapper.event.jvm_restart.email.body=The JVM was restarted.nnPlease check on its status.n
# Wrapper Windows NT/2000/XP Service Properties
# WARNING - Do not modify any of these properties when an application
# using this configuration file has been installed as a service.
# Please uninstall the service before modifying this section. The
# service can then be reinstalled.
# Name of the service
# Display name of the service
wrapper.displayname=Wisbech Pre-Production
# Description of the service
wrapper.description=Wisbech Pre-Production
# Service dependencies. Add dependencies as needed starting from 1
# Mode in which the service is installed. AUTO_START, DELAY_START or DEMAND_START
# Allow the service to interact with the desktop.
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
Wrapper-user mailing list
[hidden email]