gbo
n00b
Joined: 11 May 2007
Posts: 5
|
 Posted: Thu Jun 26, 2008 10:23 pm Post subject: [Résolu][Tomcat] pb pour lancer simultanément 2 instances |
 |
|
J'utilise tomcat v5.5.25 avec sun-jdk v1.5.0.11
J'ai dupliqué :
/etc/init.d/tomcat-5.5 en /etc/init.d/tomcat-5.5-2
/etc/conf.d/tomcat-5.5 en /etc/conf.d/tomcat-5.5-2
/var/lib/tomcat-5.5 en /var/lib/tomcat-5.5-2
avec conf -> /etc/tomcat-5.5-2
logs -> /home/var/log/tomcat-5.5-2
temp -> /home/var/tmp/tomcat-5.5-2
work -> /home/var/run/tomcat-5.5-2
Le port du second server.xml est 8105
Contenu de /etc/conf.d/tomcat-5.5-2 :
| Code: | JAVA_OPTS="-server"
JAVA_OPTS="${JAVA_OPTS} -d64"
JAVA_OPTS="${JAVA_OPTS} -Xms256m"
JAVA_OPTS="${JAVA_OPTS} -Xmx256m"
JAVA_OPTS="${JAVA_OPTS} -XX:PermSize=64m"
JAVA_OPTS="${JAVA_OPTS} -XX:MaxPermSize=64m"
JAVA_OPTS="${JAVA_OPTS} -XX:+CMSPermGenSweepingEnabled"
JAVA_OPTS="${JAVA_OPTS} -XX:+CMSClassUnloadingEnabled"
JAVA_OPTS="${JAVA_OPTS} -Dcom.sun.management.jmxremote.port=9005"
JAVA_OPTS="${JAVA_OPTS} -Dcom.sun.management.jmxremote.password.file=/var/lib/tomcat-5.5/conf/jmxremote.password"
JAVA_OPTS="${JAVA_OPTS} -Dcom.sun.management.jmxremote.access.file=/var/lib/tomcat-5.5/conf/jmxremote.access"
JAVA_OPTS="${JAVA_OPTS} -Dcom.sun.management.jmxremote.ssl=false"
JAVA_OPTS="${JAVA_OPTS} -Djava.rmi.server.hostname=xx.xx.xx.xx"
CATALINA_HOME=/usr/share/tomcat-5.5/
CATALINA_BASE=/var/lib/tomcat-5.5-2/
CATALINA_USER=tomcat
CATALINA_GROUP=tomcat
CATALINA_LIBDIR=/usr/share/tomcat-5.5/server/lib/
CLASSPATH=${CATALINA_LIBDIR}
CATALINA_TMPDIR="/home/var/tmp/tomcat-5.5-2/"
TOMCAT_START="start"
TOMCAT_STOP="stop"
CATALINA_OPTS="-Djava.library.path=/usr/lib" |
Contenu de /etc/init.d/tomcat-5.5-2 :
| Code: | # Populate JAVA_HOME
JAVA_HOME=`java-config --jre-home`
. /etc/conf.d/tomcat-5.5-2
# Set some sane defaults
if [ -z "${CATALINA_TMPDIR}" ] ; then
CATALINA_TMPDIR="${CATALINA_BASE}"/temp
...
start_helper() {
local executor=${1}
shift
local arguments="--start --quiet \
--chdir "${CATALINA_TMPDIR}" \
--chuid ${CATALINA_USER}:${CATALINA_GROUP} \
--make-pidfile --pidfile /var/run/tomcat-5.5-2.pid"
...
stop() {
ebegin "Stopping Tomcat"
init_env_vars
start-stop-daemon --stop --quiet \
--make-pidfile --pidfile /var/run/tomcat-5.5-2.pid \ |
Ne comprenant pas comment /etc/init.d/tomcat-5.5 accède aux variables TOMCAT définies dans /etc/conf.d/tomcat-5.5 j'ai inséré . /etc/conf.d/tomcat-5.5-2 dans /etc/init.d/tomcat-5.5-2
Quand j'exécute /etc/init.d/tomcat-5.5-2 start, j'obtiens :
| Code: | * Caching service dependencies ... [ ok ]
* WARNING: tomcat-5.5-2 has already been started. |
Or un ps -ef |grep tomcat me retourne :
| Code: | | tomcat 13709 23691 15 Jun26 pts/0 00:10:36 /opt/sun-jdk-1.5.0.11/bin/java -server -Xms512m -Xmx512m -XX:PermSize=128m -XX:MaxPermSize=128m -XX:+CMSPermGenSweepingEnabled -XX:+CMSClassUnloadingEnabled -Dcom.sun.management.jmxremote.port=9004 -Dcom.sun.management.jmxremote.password.file=/var/lib/tomcat-5.5/conf/jmxremote.password -Dcom.sun.management.jmxremote.access.file=/var/lib/tomcat-5.5/conf/jmxremote.access -Dcom.sun.management.jmxremote.ssl=false -Djava.rmi.server.hostname=xx.xx.xx.xx -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=/var/lib/tomcat-5.5//conf/logging.properties -Djava.library.path=/usr/lib -Djava.endorsed.dirs=/usr/share/tomcat-5.5//common/endorsed -classpath /usr/share/tomcat-5.5/server/lib/:/usr/share/tomcat-5.5//server/lib:/opt/sun-jdk-1.5.0.11/lib/tools.jar:/usr/share/tomcat-5.5//bin/bootstrap.jar:/usr/share/tomcat-5.5//bin/commons-logging-api.jar -Dcatalina.base=/var/lib/tomcat-5.5/ -Dcatalina.home=/usr/share/tomcat-5.5/ -Djava.io.tmpdir=/var/tmp/tomcat-5.5/ org.apache.catalina.startup.Bootstrap start |
Merci de votre aide.
[update du 27/06/08]
1/ J'ai trouvé comment /etc/init.d/tomcat-5.5 accède aux variables TOMCAT définies dans /etc/conf.d/tomcat-5.5 : c'est le script #!/sbin/runscript qui effectue l'opération
| Code: | # (2) Source /etc/conf.d/${SVCNAME} to get initscript-specific
# configuration (if it exists). |
2/ pour le message WARNING: tomcat-5.5-2 has already been started j'ai tenté de modifier le nom de mon SVCNAME en renommant tomcat-5.5-2 en tomcat2-5.5 (pour les fichier init.d et conf.d)... et ça marche! |
|
French
