Bug 30568 - Cannot find daemon loader
Summary: Cannot find daemon loader
Alias: None
Product: Tomcat 5
Classification: Unclassified
Component: Catalina (show other bugs)
Version: 5.0.27
Hardware: Macintosh Linux
: P3 normal with 1 vote (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
Depends on:
Reported: 2004-08-10 18:59 UTC by Justin Gombos
Modified: 2004-11-16 19:05 UTC (History)
1 user (show)


Note You need to log in before you can comment on or make changes to this bug.
Description Justin Gombos 2004-08-10 18:59:12 UTC
There are multiple defects.  Some are likely to be defects with the Gentoo 
distribution of Tomcat5, and at least one of the defects (documented below) is 
in Catalina.  For the history of installation issues, see the following two 


I spotted another report of this issue in an Apache mailing list:


Skipping the installation issues (because they may be in the scope of the 
Gentoo folks), I will go right to the problem that results following a manual 
install as per the Tomcat documentation.

Execution of:

    ./bin/jsvc -Djava.endorsed.dirs=./common/endorsed -cp ./bin/bootstrap.jar \
        -outfile ./logs/catalina.out -errfile ./logs/catalina.err \

Results in:

  jsvc.exec error: Cannot find daemon loader 
  jsvc.exec error: Service exit with a return value of 1

I see no reason why jsvc would not be able to find the Daemon Loader.  The JAR 
file is in the $CATALINA_HOME/bin folder, and looking at the table of contents 
reveals the class that jsvc cannot find.

Also, it may still be worthwhile to look at the Gentoo installation issues, 
because the ./configure script that comes packaged with Tomcat fails when 
uname -m returns "ppc64".
Comment 1 Yoav Shapira 2004-08-31 14:23:57 UTC
I don't have a Gentoo system to test.  This works for me on Solaris and RHEL by 
following the Tomcat docs, no problem.

bootstrap.jar includes commons-daemon.jar in its manifest Class Path.  If 
commons-daemon.jar is in the same directory with the proper file permissions, 
you should have no problem with this.  If you do have a problem, it's a 
configuration or installation issue, not a Tomcat bug.

Finally, please use separate Bugzilla issues for separate bugs, don't combine 
them.  For example, the ./configure script bug you report should be a separate 
issue.  (That one as I mentioned I can't test because I don't have a Gentoo 
system).  Thanks.
Comment 2 David Crossley 2004-09-05 07:44:38 UTC
I see this same issue with Tomcat-5.0.28 binary distribution (on RedHat Linux 9
and J2SDK-1.4.1).
Followed the instructions at
and get the same problems and described in this issue.

Following $CATALINA_HOME/RUNNING.txt and using startup.sh is okay.
Comment 3 Yoav Shapira 2004-09-08 19:51:52 UTC
OK, if you want, please submit doc patches for setup.xml and I'll modify that 
file so that the instructions are correct.
Comment 4 David Crossley 2004-09-09 01:33:22 UTC
Perhaps you misinterpret my comments. The documentation describes two different
ways to start Tomcat. The method described in RUNNING.txt works okay. The method
described in setup.html fails with this "daemon loader" error.
Comment 5 Yoav Shapira 2004-09-15 16:20:37 UTC
I understand your comments, I think ;)  I'm asking you to provide a diff patch 
of setup.xml so that it is correct.
Comment 6 Yoav Shapira 2004-09-27 15:33:48 UTC
OK, I've added a note to cover this situation to the setup.xml (which becomes 
setup.html) files, on both the Tomcat 5.0 and 5.5 branches.  Thanks for 
reporting this issue.