From owner-freebsd-ports@FreeBSD.ORG Thu Sep 25 05:43:25 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE02116A4B3 for ; Thu, 25 Sep 2003 05:43:25 -0700 (PDT) Received: from mailbox.rainbownet.com (mailbox.rainbownet.com [213.174.191.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2B4044047 for ; Thu, 25 Sep 2003 05:43:23 -0700 (PDT) (envelope-from aturetta@commit.it) Received: from nbangx ([192.168.29.102]) (authenticated user aturetta@rainbownet.com) by rainbownet.com (rainbownet.com [127.0.0.1]) (MDaemon.PRO.v6.8.4.R) with ESMTP id 32-md50000000576.tmp for ; Thu, 25 Sep 2003 14:40:31 +0200 Message-ID: <002701c38362$3526e140$661da8c0@lan> From: "Angelo Turetta" To: "Kang Liu" , References: <006001c3830f$6d3f29f0$0501a8c0@ssc> Date: Thu, 25 Sep 2003 14:40:31 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Authenticated-Sender: aturetta@rainbownet.com X-Spam-Processed: rainbownet.com, Thu, 25 Sep 2003 14:40:31 +0200 (not processed: message from valid local sender) X-MDRemoteIP: 192.168.29.102 X-Return-Path: aturetta@commit.it X-MDaemon-Deliver-To: ports@FreeBSD.org Subject: Re: jakarta-tomcatX: different behaviour between port and package X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Sep 2003 12:43:26 -0000 In fact you have exactly reproduced the problem !! Try to connect a browser to port 8180 in this situation, and you will see exactly nothing (just a hung connection). If you look in your /usr/local/jakarta-tomcat5.0/logs/stdout.log you'll see the error I was speaking of. The conf directory (as well as its parent and all siblings) must be owned by www:www (as correctly happens when you run 'make install' from the port), or otherwise the boot process of tomcat5 will not complete (when the server is running fine, you should see two sockets listening on ports 8005 and 8009 beside the 8180 you noticed). On the other hand tomcat4, in the same situation you have reproduced, will not start at all, and its JVM will exit after few seconds. Thanks for help. Angelo. ----- Original Message ----- From: "Kang Liu" Sent: Thursday, September 25, 2003 4:47 AM > I can not reproduce the problem you described on 5.1current. > Kang > > ipfwtest# whoami > root > ipfwtest# pkg_add jakarta-tomcat-5.0.12.tbz > ipfwtest# tomcat50ctl start > >> Reading PID file (/var/run/tomcat50.pid)... [ DONE ] > >> Starting Jakarta Tomcat 5.0.12... [ DONE ] > >> Writing PID file... [ DONE ] > ipfwtest# netstat -an |grep 8180 > tcp4 0 0 *.8180 *.* LISTEN > ipfwtest# ls -al /usr/local/jakarta-tomcat5.0/conf/ > total 78 > drwxr-xr-x 3 root wheel 512 Sep 25 10:33 . > drwxr-xr-x 11 root wheel 512 Sep 25 10:33 .. > drwxr-xr-x 3 root wheel 512 Sep 25 10:33 Catalina > -rw------- 1 www www 6804 Sep 22 21:21 catalina.policy > -rw------- 1 www www 2715 Sep 22 21:21 catalina.properties > -rw------- 1 www www 778 Sep 22 21:21 jk2.properties > -rw------- 1 www www 17429 Sep 22 21:21 server.xml > -rw-r--r-- 1 www www 310 Sep 22 21:25 tomcat-users.xml > -rw------- 1 www www 37158 Sep 22 21:21 web.xml > >