I compared the server.xml file to the one used on the production servers and it was the same except for the ip addresses. During bootup I get the failure but when I run the "Catalina.sh start" command, tomcat starts up fine.
Apache is not running though, so still no web services. [r...@localhost tomcat]# /usr/local/netomat/tomcat5.5.23/bin/catalina.sh start Using CATALINA_BASE: /usr/local/netomat/tomcat5.5.23 Using CATALINA_HOME: /usr/local/netomat/tomcat5.5.23 Using CATALINA_TMPDIR: /usr/local/netomat/tomcat5.5.23/temp Using JRE_HOME: /usr/jdk1.5.0_17 [r...@localhost tomcat]# ps -ef | grep tomcat root 3724 1 93 14:59 pts/0 00:00:05 /usr/jdk1.5.0_17/bin/java -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=/usr/local/netomat/tomcat5.5.23/conf/log ging.properties -Duser.timezone=America/New_York -server -Xms256M -Xmx1280M -Djava.awt.headless=true -Djava.endorsed.dirs=/usr/local/netomat/tomcat5.5.23/common/endorsed -classpath :/usr/local/netomat/tomcat5.5.23/bin/bootstrap.jar:/usr/local/netomat/to mcat5.5.23/bin/commons-logging-api.jar -Dcatalina.base=/usr/local/netomat/tomcat5.5.23 -Dcatalina.home=/usr/local/netomat/tomcat5.5.23 -Djava.io.tmpdir=/usr/local/netomat/tomcat5.5.23/temp org.apache.catalina.startup.Bootstrap start root 3737 3675 0 15:00 pts/0 00:00:00 grep tomcat Paul Bourget Isabella Products -----Original Message----- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: Thursday, August 26, 2010 2:33 PM To: Tomcat Users List Subject: Re: java.net.BindException: Address already in use -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Paul, On 8/26/2010 2:19 PM, Paul Bourget wrote: > Thanks for looking at this. Wouldn't the first instance have open ports > (indicated by netstat)? Or some httpd tasks (ps -ef). Yes, I would expect that. How are you launching Tomcat? I'm wondering if you're somehow launching Tomcat twice at once. Then again, one of them should succeed and the other should fail. Take the suggestions from others to modify your 'netstat' invocation to avoid showing service names instead of port numbers. Chuck has a good point: your server.xml looks like it's got some really old stuff in it. It's very possible that you've been dragging a server.xml from previous Tomcat versions around with you. Consider starting over with the server.xml that ships with Tomcat: just modify the shutdown port, AJP connector port, disable the HTTP connector, tweak the <Host> settings, and re-enable your AccessLogValve. It's unlikely to fix anything, but it will definitely clean things up. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkx2s08ACgkQ9CaO5/Lv0PBEpgCfTBKbtPqe2c+iDAOmoEaKLYJg RDYAn3KdPkwWWH+cQIqQMl/cn+B8Qfre =vFka -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
