Menu
We're using a vendor licensed copy of the Tanuki Java Service Wrapper to start their platform. It ships with wrappers for every O/S flavour and architecture and the recommended profile is a 64 bit VM with a 3 gig heap.
We're using 64 bit Redhat, but I've been unable to find a wrapper configuration option which forces the wrapper.sh script to use the wrapper-linux-x86-64 binary. The only way I have been able to get the wrapper to start in 64 bit mode is by deleting the wrapper-linux-x86-32 binary.
Is there a way to force the wrapper into 64 bit mode? Is it simply trying to choose the fastest appropriate VM setting and choosing 32 bit mode when it can because our heap is less than 4 gig?
I'd like to learn more about how the java-service-wrapper makes the 32/64 bit decision but have been unable to find anything online.
865
A service wrapper is a computer program that wraps arbitrary programs thus enabling them to be installed and run as Windows Services or Unix daemons, programs that run in the background, rather than under the direct control of a user. They are often automatically started at boot time.
Launch4j is a cross-platform tool for wrapping Java applications distributed as jars in lightweight Windows native executables.
The Java Service Wrapper uses a configuration file wrapper. conf to control the various Wrapper settings. The file also contains all of the information necessary to launch a JVM instance with the correct command line required by a given application.
what version of the wrapper are you running?
in 3.4.0 this has been improved: Changed the scripts and batch files to try to load the wrapper executable according to the system, i.e. on 64-bit systems the 64bit binary of the wrapper is attempted to be executed first and after this fails the 32 bit gets attempted to be loaded. This behaviour is primaly useful with the delta-pack of the wrapper.
cheers, christian
65
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
