Bug 37762 - Tomcat 3.3.1 port fails to start
Summary: Tomcat 3.3.1 port fails to start
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Ernst de Haan
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-05-05 07:30 UTC by Jim Pingle
Modified: 2002-05-07 12:21 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jim Pingle 2002-05-05 07:30:01 UTC
	After installing the jakarta-tomcat-3.3.1_11 port, it will fail to start using tomcat3ctl. If /usr/local/jakarta-tomcat3.3.1/bin/tomcat.sh is used to start the server, it works and behaves normally. The startup script /usr/local/etc/rc.d/020.jakarta-tomcat3.sh fails also (because it calls tomcat3ctl.)

When using tomcat3ctl the following error appears in /usr/local/jakarta-tomcat3.3.1/logs/stderr.log:

Exception in thread "main" java.util.zip.ZipException: No such file or directory
        at java.util.zip.ZipFile.open(Native Method)
        at java.util.zip.ZipFile.<init>(ZipFile.java:110)
        at java.util.jar.JarFile.<init>(JarFile.java:115)
        at java.util.jar.JarFile.<init>(JarFile.java:57)

Fix: 

Temporary workaround, use /usr/local/jakarta-tomcat3.3.1/bin/tomcat.sh to start the tomcat process.
How-To-Repeat: cd /usr/ports/www/jakarta-tomcat3
make install
/usr/local/etc/rc.d/020.jakarta-tomcat3.sh start
cat /usr/local/jakarta-tomcat3.3.1/logs/stderr.log
Comment 1 Ernst de Haan freebsd_committer freebsd_triage 2002-05-06 08:43:44 UTC
Responsible Changed
From-To: freebsd-ports->znerd

I'll handle this. I'm the maintainer.
Comment 2 Ernst de Haan freebsd_committer freebsd_triage 2002-05-06 09:42:44 UTC
State Changed
From-To: open->patched

Fixed. Waiting for confirmation from the originator.
Comment 3 Ernst de Haan freebsd_committer freebsd_triage 2002-05-07 12:21:27 UTC
State Changed
From-To: patched->closed

Received confirmation that the problem is fixed. 
Thanks again!