java-service-wrapper

Where to pass runtime argument in wrapper.conf file in java service wrapper?

Hi All, Iam trying to create window service for my jar application. Application needs an argument and System property value while runtime. I dont know where to give argument value and system variable value in wrapper.conf file. please help me. I am getting the below error wrapper | Launching a JVM... jvm 1 | WrapperManager: Initiali...

appassembler and long classpath

I am using maven appassembler to create my assembly. My classpath is too long and I get "The input line is too long." The suggestion here is to use booter windows platform, but I'm constrained to use Java Service Wrapper. Any way I can use java6 wildcarded classpath and java service wrapper? ...

is appassembler plugin broken for java service wrapper on windows 64bit?

Hi I'm developing on 32bit windows and am using appassembler to create a java service wrapper assembly, and it works ok. But I need to also create a 64bit assembly for deployment to a dev server. In the following config I have substituted the 32bit platform with the 64bit, see the <includes> section. But it no longer places the wrapper ...

Java service wrapper and additional application command line parameters

I'm currently using java service wrapper to wrap a java application that I've developed. I'm needing to ability to pass in additional command line parameters to my application through the java service wrapper. Pretend my app is called myapp and I've setup java service wrapper so that the script I run to start is called myapp. I'd like...

How does the java-service-wrapper decide whether to use the 32 or 64 bit VM?

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 scri...

Java Service Wrapper: socket not open, so packet not sent SERVICE_CONTROL_CODE : 4

We're using Java Service Wrapper and something weird is going on: I get the following lines repeated in the wrapper log file until someone manualy kills the process tree. DEBUG | wrapperp | 2010/10/13 11:57:10 | socket not open, so packet not sent SERVICE_CONTROL_CODE : 4 DEBUG | wrapper | 2010/10/13 11:57:10 | ServiceControlHand...