Tools Java Service Wrapper. This page provides some useful information on running the ActiveMQ broker as a windows-NT service or a daemon thread in Linux or Unix systems. 64bit 4gb memory limit. The ActiveMQ distribution uses an older and free community release of the service wrapper library.
Customer Service Customer Experience Point of Sale Lead Management Event Management Survey. Accounting Billing and Invoicing Budgeting Payment Processing Expense Report. Application Development. Application Development.
Licensing Overview
Licensing Overview
Java Wrapper Class
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. 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 Windows Service Wrapper
Java Service Wrapper Examples
The Java Service Wrapper uses a configuration file wrapper.conf to control the various Wrapper settings. For example: 10m = 10 megabytes. Wrapper.logfile.maxsize=0 # Maximum number of rolled log files which will be allowed before old # files are deleted. The default value of 0 implies no limit.
