Michael,
Were you referring to the 3 process instances of Tomcat or the startup
problem? I just upgraded tomcat5.5 to tomcat5.5.26-3 and the startup script
problem appears to have been fixed, however I still see 3 tomcat processes
loading when doing a ps -ef | grep tomcat
Is this behavior expected? Will it take up 3X the memory because it loads 3
times?
I will know more tommorow when I start deploying applications to this test
box.
I appreciate your help.
Regards
John D
ex.:
ha-test1:/var/lib/heartbeat/crm# ps -ef | grep tomcat
root 30434 1 0 16:27 ?00:00:00 /usr/bin/jsvc -user tomcat55
-cp
/usr/share/java/commons-daemon.jar:/usr/share/tomcat5.5/bin/bootstrap.jar:/usr/share/tomcat5.5/bin/commons-logging-api.jar
-outfile SYSLOG -errfile SYSLOG -pidfile /var/run/tomcat5.5.pid
-Djava.awt.headless=true -Xmx128M
-Djava.endorsed.dirs=/usr/share/tomcat5.5/common/endorsed
-Dcatalina.base=/var/lib/tomcat5.5 -Dcatalina.home=/usr/share/tomcat5.5
-Djava.io.tmpdir=/var/lib/tomcat5.5/temp -Djava.security.manager
-Djava.security.policy=/var/lib/tomcat5.5/conf/catalina.policy
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
-Djava.util.logging.config.file=/var/lib/tomcat5.5/conf/logging.properties
org.apache.catalina.startup.Bootstrap
root 30435 30434 0 16:27 ?00:00:00 /usr/bin/jsvc -user tomcat55
-cp
/usr/share/java/commons-daemon.jar:/usr/share/tomcat5.5/bin/bootstrap.jar:/usr/share/tomcat5.5/bin/commons-logging-api.jar
-outfile SYSLOG -errfile SYSLOG -pidfile /var/run/tomcat5.5.pid
-Djava.awt.headless=true -Xmx128M
-Djava.endorsed.dirs=/usr/share/tomcat5.5/common/endorsed
-Dcatalina.base=/var/lib/tomcat5.5 -Dcatalina.home=/usr/share/tomcat5.5
-Djava.io.tmpdir=/var/lib/tomcat5.5/temp -Djava.security.manager
-Djava.security.policy=/var/lib/tomcat5.5/conf/catalina.policy
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
-Djava.util.logging.config.file=/var/lib/tomcat5.5/conf/logging.properties
org.apache.catalina.startup.Bootstrap
tomcat55 30438 30434 19 16:27 ?00:00:07 /usr/bin/jsvc -user tomcat55
-cp
/usr/share/java/commons-daemon.jar:/usr/share/tomcat5.5/bin/bootstrap.jar:/usr/share/tomcat5.5/bin/commons-logging-api.jar
-outfile SYSLOG -errfile SYSLOG -pidfile /var/run/tomcat5.5.pid
-Djava.awt.headless=true -Xmx128M
-Djava.endorsed.dirs=/usr/share/tomcat5.5/common/endorsed
-Dcatalina.base=/var/lib/tomcat5.5 -Dcatalina.home=/usr/share/tomcat5.5
-Djava.io.tmpdir=/var/lib/tomcat5.5/temp -Djava.security.manager
-Djava.security.policy=/var/lib/tomcat5.5/conf/catalina.policy
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
-Djava.util.logging.config.file=/var/lib/tomcat5.5/conf/logging.properties
org.apache.catalina.startup.Bootstrap
root 30583 10235 0 16:28 pts/100:00:00 grep tomcat
On Fri, May 16, 2008 at 2:48 AM, Michael Koch [EMAIL PROTECTED] wrote:
On Thu, May 15, 2008 at 03:06:39PM +0100, Paul Cager wrote:
John Davos wrote:
Good Day All,
I installed tomcat5.5.26-1on testing and unstable and the startup
script
(/etc/init.d/tomcat5.5) doesn't start tomcat and exits without output
in the
log or at console. I started with a fresh install of debian testing
I know this method of starting tomcat works with tomcat5.5.20-2etch2
there
are too many differences that I can't decipher between the startup
scripts
of the two versions for me to fix it myself.
Any info or suggestions would be greatly appreciated, thank you for
your
time and effort!
This sounds like
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=477363. If you have a
look at that bug report, someone has suggested a patch as follows:
fixed the bug by adding an appropriate entry for
commons-logging-api.jar to the CLASSPATH of jsvc. Hence I changed line
122 of /etc/init.d/tomcat5.5 to:
JSVC_CLASSPATH=/usr/share/java/commons-daemon.jar:
$CATALINA_HOME/bin/bootstrap.jar:
$CATALINA_HOME/bin/commons-logging-api.jar
(Linebreaks added for the sake of clarity. In the original file this is
all on one line, with no whitespace in between.)
I expect that's the problem here, but please let us know if not.
That's already solved in SVN in a different way. Upload comes soon.
Cheers,
Michael
___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
