In my traffic logs, I still notice a high interest in my post for the Java Service Wrapper. So I hereby provide a more current version of the Tanuki Java Service Wrapper for Windows x64 (Community Edition).
Also, please note:
Read the rest of this entryDue to popular demand on my other post including the build process, I hereby provide the compiled version of the Tanuki Java Service Wrapper 3.4.1 for Windows x64 (Community Edition) for you to download. The software was built using the instructions included in my other post.
Use this package at your own risk, I provide no support or guarantee that this software works as advertised.
This software is provided “AS IS” and any expressed or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed.
To run the Service Wrapper, extract the following three files from the archive:
Download: wrapper_3.4.1_krenger_build.zip (aka wrapper-windows-x86-64-3.4.1.zip)
Newer versions: Newer versions of the wrapper are available here.
The only thing I ask in return is a comment if this actually helped you :)
To launch any Java program as a service, you might have to use a wrapper. This article shows how to build a current release of the Tanuki Service Wrapper (x64) from source. Tanuki Software provides three versions of the Java Service wrapper:
The paid versions of the wrapper require the configuration file to contain a machine-specific license key in order to function. When you use any x64 version of Windows as your host system, you are forced to either buy licenses or build the Wrapper from source, since they do not provide the binaries for the Community Edition. So here, we are going to build the Community Edition from source.
Update: I added a compiled version for Windows x64 in another post
Newer versions: Newer versions of the wrapper are available here.
Today I wondered how my newly purchased Virtual Server performs under load. I am currently using lighttpd as a webserver and MySQL as the database for WordPress. I already knew that MySQL features the Query Cache, which stores the result of issued queries in memory (Oracle’s equivalent of this would be the Result Cache in Oracle 11g). I wondered how much this feature could improve performance on a normal WordPress blog.
I quickly wrote a small Java program to query my website (source code available here: TestWebPerfo.java) and retrieve the performance metrics from the HTML source code. I then ran it 500 times to get my metrics without the Query Cache turned on. Average time for building the website: 0.115 seconds.
My name is Simon Krenger, I am a Technical Account Manager (TAM) at Red Hat. I advise our customers in using Kubernetes, Containers, Linux and Open Source.