Hello Tomcat World! Thanks Chuck and Michael. This is the answer for Michael:
That's like you find out your car has no wheels. You said you've
manipulated Tomcat's startup script. Don't do that. Make a clean
install and it should work.
Yes, I did, a complete clean installation of Tomcat 6.0.18. I downloaded and
put it into the /opt directory. Then, I edit the catalina.properties, wich has
the following sentence:
common.loader=${catalina.home}/lib,${catalina.home}/lib/*.jar
I read the link you posted me, but the comments in the catalinal.properties has
no example with "file:///" so I did not write like this. I added to this line
the path to the db2 jdbc driver. The current sentence is this
one:
common.loader=${catalina.home}/lib,${catalina.home}/lib/*.jar,/opt/java/jdk/jre/lib/ext/*.jar
¿Is this right or do I need to include "file:///"?
> 2) About an earlier Tomcat: I just downloaded the 6.0.18 version and
> catalina.sh it's running ok (but I have not put my webapp there yet).
Careful! :-)
I did that because one of you recommend me to do that. Why do you say careful?
Is this a bad practice? Should I use the startup.sh ??It's not considered good
practice to have a service run as root when
there is no need to do so. The root user is very powerful, so it's
potentially dangerous expose a process run as root to the world.
Well, in this
new phase of using Tomcat, I am not running it as root, just as common user
and it's working fine, but the DB2 connection deal is still causing me troubles.
Thanks for all. Now I need to learn how to do a pooling of connections. Any
comments?
I really apreciate your time for answer me.
Ariela
¡Todo sobre Amor y Sexo!
La guía completa para tu vida en Mujer de Hoy.
http://mx.mujer.yahoo.com/
