Bug#314291: marked as done (tomcat doesnt startup)

Debian Bug Tracking System owner at bugs.debian.org
Mon Sep 26 19:48:15 UTC 2005


Your message dated Mon, 26 Sep 2005 21:45:55 +0200
with message-id <43384FF3.4050301 at gmx.de>
and subject line recent kaffe uploads has fixed the tomcat4 security manager issue
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 15 Jun 2005 15:03:28 +0000
>From seppepeeters at gmail.com Wed Jun 15 08:03:28 2005
Return-path: <seppepeeters at gmail.com>
Received: from nproxy.gmail.com [64.233.182.200] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1DiZQN-0002WP-00; Wed, 15 Jun 2005 08:03:28 -0700
Received: by nproxy.gmail.com with SMTP id l37so106347nfc
        for <submit at bugs.debian.org>; Wed, 15 Jun 2005 08:02:56 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type;
        b=Q0vusdh4hkvQmhRNsHWdDepY2YDk1iEYvPYRAQLCbV+pipieQhwA5Z1RFYX+tOaztT9VOGFtzecn5Vx0dxH6f4PTt+im6tYYiubdFuII3dl+VAVxyGFe1rqNcpdbenLhWjfIo7pieLPagYtDuQRRKPTuoC4xd/zkNu+ykR8S2FY=
Received: by 10.48.237.12 with SMTP id k12mr90387nfh;
        Wed, 15 Jun 2005 08:02:56 -0700 (PDT)
Received: by 10.48.248.9 with HTTP; Wed, 15 Jun 2005 08:02:56 -0700 (PDT)
Message-ID: <7d009680050615080291b251b at mail.gmail.com>
Date: Wed, 15 Jun 2005 17:02:56 +0200
From: seppe peeters <seppepeeters at gmail.com>
Reply-To: seppe peeters <seppepeeters at gmail.com>
To: submit at bugs.debian.org
Subject: tomcat doesnt startup
Mime-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_1338_25251233.1118847776394"
Delivered-To: submit at bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-5.5 required=4.0 tests=BAYES_00,HAS_PACKAGE,
	HTML_10_20,HTML_MESSAGE autolearn=no 
	version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

------=_Part_1338_25251233.1118847776394
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

package: tomcat4
version: 4.1.31-3
branch: unstable


$ sudo /etc/init.d/tomcat4 start
Starting Tomcat 4.1 servlet engine using Java from /usr/lib/j2sdk1.5-sun:=
=20
tomcat4.
$ sudo /etc/init.d/tomcat4 stop
Stopping Tomcat 4.1 servlet engine: (not running).


$ sudo /usr/share/tomcat4/bin/startup.sh
Using CATALINA_BASE: /usr/share/tomcat4
Using CATALINA_HOME: /usr/share/tomcat4
Using CATALINA_TMPDIR: /usr/share/tomcat4/temp
Using JAVA_HOME: /usr/lib/j2sdk1.5-sun
$ sudo /usr/share/tomcat4/bin/shutdown.sh
Using CATALINA_BASE: /usr/share/tomcat4
Using CATALINA_HOME: /usr/share/tomcat4
Using CATALINA_TMPDIR: /usr/share/tomcat4/temp
Using JAVA_HOME: /usr/lib/j2sdk1.5-sun
Catalina.stop: java.net.ConnectException: Connection refused
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:364)
at java.net.Socket.connect(Socket.java:507)
at java.net.Socket.connect(Socket.java:457)
at java.net.Socket.<init>(Socket.java:365)
at java.net.Socket.<init>(Socket.java:178)
at org.apache.catalina.startup.Catalina.stop(Catalina.java:532)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:352)
at org.apache.catalina.startup.Catalina.process(Catalina.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav=
a
:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:156)


I've also tested it on my server. Wich uses kaffe instead of j2sdk with the=
=20
same results.

Basically i can't get tomcat to run and answer to port 8180. This is a port=
=20
in the default server.xml file.=20
It is possible i have to change the default configuration.

I've seen on the internet about the same error attributed to a syntax error=
.=20
I couldn't find any wrong "=20
in /etc/tomcat4/server.xml and /etc/tomcat4/web.xml.

I hope this qualifies as bug. And is fixed soon.


Thanks in advance for the positive response,
Seppe Peeters

------=_Part_1338_25251233.1118847776394
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<br>
package: tomcat4<br>
version: 4.1.31-3<br>
branch: unstable<br>
<br>
<br>
$ sudo /etc/init.d/tomcat4 start<br>
Starting Tomcat 4.1 servlet engine using Java from /usr/lib/j2sdk1.5-sun: t=
omcat4.<br>
$ sudo /etc/init.d/tomcat4 stop<br>
Stopping Tomcat 4.1 servlet engine: (not running).<br>
<br>
<br>
$ sudo /usr/share/tomcat4/bin/startup.sh<br>
Using CATALINA_BASE:&nbsp;&nbsp; /usr/share/tomcat4<br>
Using CATALINA_HOME:&nbsp;&nbsp; /usr/share/tomcat4<br>
Using CATALINA_TMPDIR: /usr/share/tomcat4/temp<br>
Using JAVA_HOME:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /usr/lib/j2sdk1.5-sun<=
br>
$ sudo /usr/share/tomcat4/bin/shutdown.sh<br>
Using CATALINA_BASE:&nbsp;&nbsp; /usr/share/tomcat4<br>
Using CATALINA_HOME:&nbsp;&nbsp; /usr/share/tomcat4<br>
Using CATALINA_TMPDIR: /usr/share/tomcat4/temp<br>
Using JAVA_HOME:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /usr/lib/j2sdk1.5-sun<=
br>
Catalina.stop: java.net.ConnectException: Connection refused<br>
java.net.ConnectException: Connection refused<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at java.net.PlainSocketImpl.sock=
etConnect(Native Method)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at java.net.PlainSocketImpl.doCo=
nnect(PlainSocketImpl.java:333)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at java.net.PlainSocketImpl.conn=
ectToAddress(PlainSocketImpl.java:195)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at java.net.PlainSocketImpl.conn=
ect(PlainSocketImpl.java:182)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at java.net.SocksSocketImpl.conn=
ect(SocksSocketImpl.java:364)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at java.net.Socket.connect(Socke=
t.java:507)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at java.net.Socket.connect(Socke=
t.java:457)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at java.net.Socket.&lt;init&gt;(=
Socket.java:365)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at java.net.Socket.&lt;init&gt;(=
Socket.java:178)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.catalina.startup.C=
atalina.stop(Catalina.java:532)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.catalina.startup.C=
atalina.execute(Catalina.java:352)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.catalina.startup.C=
atalina.process(Catalina.java:129)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at sun.reflect.NativeMethodAcces=
sorImpl.invoke0(Native Method)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at sun.reflect.NativeMethodAcces=
sorImpl.invoke(NativeMethodAccessorImpl.java:39)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp=
l.java:25)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at java.lang.reflect.Method.invo=
ke(Method.java:585)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.catalina.startup.B=
ootstrap.main(Bootstrap.java:156)<br>
<br>
<br>
I've also tested it on my server.&nbsp; Wich uses kaffe instead of j2sdk wi=
th the same results.<br>
<br>
Basically i can't get tomcat to run and answer to port 8180.&nbsp; This is =
a port in the default server.xml file.&nbsp; <br>
It is possible i have to change the default configuration.<br>
<br>
I've seen on the internet about the same error attributed to a syntax error=
.&nbsp; I couldn't find any wrong &quot; <br>
in /etc/tomcat4/server.xml and /etc/tomcat4/web.xml.<br>
<br>
I hope this qualifies as bug.&nbsp; And is fixed soon.<br>
<br>
<br>
Thanks in advance for the positive response,<br>
Seppe Peeters<br>
<br>
<br>

------=_Part_1338_25251233.1118847776394--

---------------------------------------
Received: (at 314291-done) by bugs.debian.org; 26 Sep 2005 19:44:22 +0000
>From WBaer at gmx.de Mon Sep 26 12:44:22 2005
Return-path: <WBaer at gmx.de>
Received: from pop.gmx.de (mail.gmx.net) [213.165.64.20] 
	by spohr.debian.org with smtp (Exim 3.36 1 (Debian))
	id 1EJyti-0004YB-00; Mon, 26 Sep 2005 12:44:22 -0700
Received: (qmail invoked by alias); 26 Sep 2005 19:43:51 -0000
Received: from p54819D64.dip0.t-ipconnect.de (EHLO [192.168.0.203]) [84.129.157.100]
  by mail.gmx.net (mp031) with SMTP; 26 Sep 2005 21:43:51 +0200
X-Authenticated: #1941950
Message-ID: <43384FF3.4050301 at gmx.de>
Date: Mon, 26 Sep 2005 21:45:55 +0200
From: Wolfgang Baer <WBaer at gmx.de>
User-Agent: Debian Thunderbird 1.0.6 (X11/20050802)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: 323596-done at bugs.debian.org,  314291-done at bugs.debian.org
Subject: recent kaffe uploads has fixed the tomcat4 security manager issue
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Delivered-To: 314291-done at bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
	version=2.60-bugs.debian.org_2005_01_02

Hi,

the recent kaffe uploads have fixed the tomcat4 security manager issue
and I will hereby close two of the three bug reports for this issue.

The third bugreport will stay open tagged as sarge. I think that
it will help people on sarge systems, which are running into this problem
to solve it (and don't further reporting the issue).

Regards,
Wolfgang



More information about the pkg-java-maintainers mailing list