You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Dieter Schmidt <di...@visualmusix.com> on 2006/05/04 17:49:49 UTC
Crashing Tomcat 4.1 on Debain
Hello all,
I am fighting the whole day log against Tomcat 4.1 and can't get it
started.
I'm running a debian system Kernel 2.4.27-2-686-smp sarge on an Intel
Dual Xeon. Tomcat is needed as basis for the Installation of OpenNMS, so
I followed the the installation manual of OpenNMS at
http://sourceforge.net/docman/display_doc.php?docid=23937&group_id=4141#N100BA.
On my blank system I installed via apt-get
java-common,
sun-jdk.14-installer and build an jdk1.4.2_10.deb-packet with
build-sun-jdk14.
After installing the JDK I made an apt-get tomcat4 and everything went fine.
(btw: $JAVA_HOME is set correctly to /usr/lib/j2sdk1.4/)
I called the /etc/init.d/tomcat start an just for a second in ps output
I can see:
tomcat4 19995 0.0 0.0 6152 1452 pts/1 S 17:36 0:00
/usr/sbin/rotatelogs /var/lib/tomcat4/logs/catalina_%F.log 86400
tomcat4 20002 0.0 0.1 271304 3716 pts/1 R 17:36 0:00
/usr/lib/j2sdk1.4/bin/java -Djava.awt.headless=true -Xmx128M
-Djava.endorsed.dirs=/usr/share/tomcat4/common/endorsed -classpath
/usr/lib/j2sdk1.4/lib/tools.jar:/usr/lib/j2sdk1.4/jre//lib/jcert.jar:/usr/lib/j2sdk1.4/jre//lib/jnet.jar:/usr/lib/j2sdk1.4/jre//lib/jsse.jar:/usr/share/tomcat4/bin/bootstrap.jar
-Djava.security.manager
-Djava.security.policy==/var/lib/tomcat4/conf/catalina.policy
-Dcatalina.base=/var/lib/tomcat4 -Dcatalina.home=/usr/share/tomcat4
-Djava.io.tmpdir=/var/lib/tomcat4/temp
org.apache.catalina.startup.Bootstrap start
The 2nd process (i think ist the server,right?) dies without any notice
in the logs.
<--- logfile content -->
at
org.apache.catalina.core.StandardService.stop(StandardService.java:499)
at
org.apache.catalina.core.StandardServer.stop(StandardServer.java:2178)
at org.apache.catalina.startup.Catalina.start(Catalina.java:494)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:350)
at org.apache.catalina.startup.Catalina.process(Catalina.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:156)
<--- --->
I also tried to start the Server by running
/usr/share/tomcat4/bin/catalina.sh start. or startup.sh both way only
produce a
root 20932 0.0 0.0 2312 1104 pts/1 S 17:41 0:00 /bin/sh
/usr/share/tomcat4/bin/catalina.sh start
but no ports are opened nether 8080 nor 8180.
What's going wrong? What am I doing wrong?
Please help!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Crashing Tomcat 4.1 on Debain
Posted by Min Huang <mh...@minformix.org>.
I didn't notice that I had the wrong topic in my email.
My sincerest apologies!
Marc Farrow wrote:
> Min,
>
> You commited what is known as thread stealing. Read the FAQs. When you
> want to submit a new question/topic then send a clean email to
> users@tomcat.apache.org and DO NOT REPLY to someone else's post.
>
> On 5/4/06, Min Huang <mh...@minformix.org> wrote:
>>
>> I've been stumped on a (what seems to be) a simple classpath
>> problem for nearly a day now, and I am feeling like an idiot
>> for not being able to figure it out.
>>
>> I wrote a jar that is bundled within a war, as part of a web
>> app that was written long ago. My application jar references a
>> bunch of configuration files, all located inside the jar.
>>
>> When testing the app, it seems that none of my configuration
>> files within the jar can be found, causing my code to fail. I'm using
>> Log4J, Hibernate3, and Commons Configuration - none of whose
>> configuration files are found.
>>
>> However, I decided to play around with the problem a little bit,
>> and I found that if I unpack my jar into the /WEB-INF/classes
>> folder, and the tomcat log shows that all of my configuration files,
>> save for my hibernate.cfg.xml, are found.
>>
>> Now, a few twists to make things interesting:
>> - I'm using Hibernate 3, but the old webapp is using Hibernate2, which
>> I assumed wouldn't cause namespace conflicts because they are located
>> in different packages.
>> - The Hibernate2 configuration file is located in /WEB-INF/classes
>> and can be found. *My* Hibernate3 configuration file is located within
>> my jar in /WEB-INF/lib, and can't be found.
>> - My configuration files aren't located in the base path within the
>> jar, if that makes a difference.
>> - My application jar runs fine on its own if I make a quick and dirty
>> JSP with a scriplet that executes the code.
>>
>> Is this a classpath issue? Do different versions of Hibernate just
>> not play around nicely with each other? Will I have hair left before
>> this problem is resolved?
>>
>> If anybody knows, please tell!
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>
>
> --
> Marc Farrow
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Crashing Tomcat 4.1 on Debain
Posted by Marc Farrow <ma...@gmail.com>.
Min,
You commited what is known as thread stealing. Read the FAQs. When you
want to submit a new question/topic then send a clean email to
users@tomcat.apache.org and DO NOT REPLY to someone else's post.
On 5/4/06, Min Huang <mh...@minformix.org> wrote:
>
> I've been stumped on a (what seems to be) a simple classpath
> problem for nearly a day now, and I am feeling like an idiot
> for not being able to figure it out.
>
> I wrote a jar that is bundled within a war, as part of a web
> app that was written long ago. My application jar references a
> bunch of configuration files, all located inside the jar.
>
> When testing the app, it seems that none of my configuration
> files within the jar can be found, causing my code to fail. I'm using
> Log4J, Hibernate3, and Commons Configuration - none of whose
> configuration files are found.
>
> However, I decided to play around with the problem a little bit,
> and I found that if I unpack my jar into the /WEB-INF/classes
> folder, and the tomcat log shows that all of my configuration files,
> save for my hibernate.cfg.xml, are found.
>
> Now, a few twists to make things interesting:
> - I'm using Hibernate 3, but the old webapp is using Hibernate2, which
> I assumed wouldn't cause namespace conflicts because they are located
> in different packages.
> - The Hibernate2 configuration file is located in /WEB-INF/classes
> and can be found. *My* Hibernate3 configuration file is located within
> my jar in /WEB-INF/lib, and can't be found.
> - My configuration files aren't located in the base path within the
> jar, if that makes a difference.
> - My application jar runs fine on its own if I make a quick and dirty
> JSP with a scriplet that executes the code.
>
> Is this a classpath issue? Do different versions of Hibernate just
> not play around nicely with each other? Will I have hair left before
> this problem is resolved?
>
> If anybody knows, please tell!
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
--
Marc Farrow
Re: Crashing Tomcat 4.1 on Debain
Posted by Min Huang <mh...@minformix.org>.
I've been stumped on a (what seems to be) a simple classpath
problem for nearly a day now, and I am feeling like an idiot
for not being able to figure it out.
I wrote a jar that is bundled within a war, as part of a web
app that was written long ago. My application jar references a
bunch of configuration files, all located inside the jar.
When testing the app, it seems that none of my configuration
files within the jar can be found, causing my code to fail. I'm using
Log4J, Hibernate3, and Commons Configuration - none of whose
configuration files are found.
However, I decided to play around with the problem a little bit,
and I found that if I unpack my jar into the /WEB-INF/classes
folder, and the tomcat log shows that all of my configuration files,
save for my hibernate.cfg.xml, are found.
Now, a few twists to make things interesting:
- I'm using Hibernate 3, but the old webapp is using Hibernate2, which
I assumed wouldn't cause namespace conflicts because they are located
in different packages.
- The Hibernate2 configuration file is located in /WEB-INF/classes
and can be found. *My* Hibernate3 configuration file is located within
my jar in /WEB-INF/lib, and can't be found.
- My configuration files aren't located in the base path within the
jar, if that makes a difference.
- My application jar runs fine on its own if I make a quick and dirty
JSP with a scriplet that executes the code.
Is this a classpath issue? Do different versions of Hibernate just
not play around nicely with each other? Will I have hair left before
this problem is resolved?
If anybody knows, please tell!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Crashing Tomcat 4.1 on Debain
Posted by Dieter Schmidt <di...@visualmusix.com>.
Leon Rosenberg schrieb:
> I think the easiest way is to throw away the packages and download and
> install a CLEAN jdk from sun and a tar.gz-iped tomcat version from
> tomcat.apache.org.
>
> I also use debian (etch) and everything java-related in debian
> packages is simply sick.... :-)
>
> regards
> Leon
>
> P.S. Of course you could try to fix the packages, but is it worth
> trying? You don't want your tomcat to be updated by apt-get upgrade do
> you?
Hi Leon,
thanks for you tip. I installed all packages by apt-get renamed the
directories and put there the new libraries from Sun and Apache. Now
tomcat works.
The last thing I need now is a working server.xml for OpenNMS.
Thanks a lot. (an the java packages are sich.)
grtx
Dieter
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Crashing Tomcat 4.1 on Debain
Posted by Leon Rosenberg <ro...@googlemail.com>.
I think the easiest way is to throw away the packages and download and
install a CLEAN jdk from sun and a tar.gz-iped tomcat version from
tomcat.apache.org.
I also use debian (etch) and everything java-related in debian
packages is simply sick.... :-)
regards
Leon
P.S. Of course you could try to fix the packages, but is it worth
trying? You don't want your tomcat to be updated by apt-get upgrade do
you?
On 5/4/06, Dieter Schmidt <di...@visualmusix.com> wrote:
> Hello all,
>
> I am fighting the whole day log against Tomcat 4.1 and can't get it
> started.
> I'm running a debian system Kernel 2.4.27-2-686-smp sarge on an Intel
> Dual Xeon. Tomcat is needed as basis for the Installation of OpenNMS, so
> I followed the the installation manual of OpenNMS at
> http://sourceforge.net/docman/display_doc.php?docid=23937&group_id=4141#N100BA.
>
> On my blank system I installed via apt-get
> java-common,
> sun-jdk.14-installer and build an jdk1.4.2_10.deb-packet with
> build-sun-jdk14.
> After installing the JDK I made an apt-get tomcat4 and everything went fine.
> (btw: $JAVA_HOME is set correctly to /usr/lib/j2sdk1.4/)
>
> I called the /etc/init.d/tomcat start an just for a second in ps output
> I can see:
> tomcat4 19995 0.0 0.0 6152 1452 pts/1 S 17:36 0:00
> /usr/sbin/rotatelogs /var/lib/tomcat4/logs/catalina_%F.log 86400
> tomcat4 20002 0.0 0.1 271304 3716 pts/1 R 17:36 0:00
> /usr/lib/j2sdk1.4/bin/java -Djava.awt.headless=true -Xmx128M
> -Djava.endorsed.dirs=/usr/share/tomcat4/common/endorsed -classpath
> /usr/lib/j2sdk1.4/lib/tools.jar:/usr/lib/j2sdk1.4/jre//lib/jcert.jar:/usr/lib/j2sdk1.4/jre//lib/jnet.jar:/usr/lib/j2sdk1.4/jre//lib/jsse.jar:/usr/share/tomcat4/bin/bootstrap.jar
> -Djava.security.manager
> -Djava.security.policy==/var/lib/tomcat4/conf/catalina.policy
> -Dcatalina.base=/var/lib/tomcat4 -Dcatalina.home=/usr/share/tomcat4
> -Djava.io.tmpdir=/var/lib/tomcat4/temp
> org.apache.catalina.startup.Bootstrap start
>
> The 2nd process (i think ist the server,right?) dies without any notice
> in the logs.
> <--- logfile content -->
> at
> org.apache.catalina.core.StandardService.stop(StandardService.java:499)
> at
> org.apache.catalina.core.StandardServer.stop(StandardServer.java:2178)
> at org.apache.catalina.startup.Catalina.start(Catalina.java:494)
> at org.apache.catalina.startup.Catalina.execute(Catalina.java:350)
> at org.apache.catalina.startup.Catalina.process(Catalina.java:129)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:156)
> <--- --->
> I also tried to start the Server by running
> /usr/share/tomcat4/bin/catalina.sh start. or startup.sh both way only
> produce a
> root 20932 0.0 0.0 2312 1104 pts/1 S 17:41 0:00 /bin/sh
> /usr/share/tomcat4/bin/catalina.sh start
> but no ports are opened nether 8080 nor 8180.
>
> What's going wrong? What am I doing wrong?
> Please help!
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Crashing Tomcat 4.1 on Debain
Posted by bossert <o....@gmail.com>.
Yoo,
Please specify your problem..... how are you trying to start tomcat?
Greetings O.
On Mon, 2006-05-08 at 10:40 -0300, Gustavo Noronha wrote:
> 2006/5/4, Dieter Schmidt <di...@visualmusix.com>:
> >
> > Hello all,
> >
> > I am fighting the whole day log against Tomcat 4.1 and can't get it
> > started.
>
>
> I noticed, the first time I installed it, that the tomcat4 package in Debian
> would only work if you have tomcat4-webapps installed. I forgot if I found a
> solution besides installilng the package (maybe removing some references to
> the test apps from some .xml)
>
> Maybe that's your problem, maybe not, do try installing the package.
>
> See ya,
>
> --
> Gustavo Noronha Silva
> Coordenação de Segurança e Sustentação
> Ministério do Desenvolvimento Social - Brasil
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Crashing Tomcat 4.1 on Debain
Posted by Gustavo Noronha <gu...@gmail.com>.
2006/5/4, Dieter Schmidt <di...@visualmusix.com>:
>
> Hello all,
>
> I am fighting the whole day log against Tomcat 4.1 and can't get it
> started.
I noticed, the first time I installed it, that the tomcat4 package in Debian
would only work if you have tomcat4-webapps installed. I forgot if I found a
solution besides installilng the package (maybe removing some references to
the test apps from some .xml)
Maybe that's your problem, maybe not, do try installing the package.
See ya,
--
Gustavo Noronha Silva
Coordenação de Segurança e Sustentação
Ministério do Desenvolvimento Social - Brasil