This is really weird; I figured out the issue.
The jsvc app choked on the name of the jar file.
I put the date the jar file is created between parens and on my dev machine
I tried to start the file directly and it failed. On the production machine
I have a symbolic link with a plain name
On 19 November 2010 08:55, pieter.br...@gmail.com
pieter.br...@gmail.com wrote:
This is really weird; I figured out the issue.
The jsvc app choked on the name of the jar file.
I put the date the jar file is created between parens and on my dev machine
I tried to start the file directly and
On 11/18/2010 12:09 PM, pieter.br...@gmail.com wrote:
I have an 'uber' jar which contains the jars for all dependencies. On my
server the following command works fine:
sudo jsvc -home /usr/lib/jvm/java-6-openjdk -cp
I browsed the fat jar and it contains this:
- /org/apache/commons/daemon
- /org/apache/commons/daemon/support/
The DaemonLoader.class is in the support package.
The other thing (not sure if this is relevant) is that I don't have a class
that implements the Daemon interface. My class just has
On 11/18/2010 02:44 PM, pieter.br...@gmail.com wrote:
I browsed the fat jar and it contains this:
- /org/apache/commons/daemon
- /org/apache/commons/daemon/support/
The DaemonLoader.class is in the support package.
The other thing (not sure if this is relevant) is that I don't have a class
