Re: New Tomcat install on a customer box: Tomcat 7.0.25 starts, then throws an exception and shuts down, and I don't know why.

Could be another Tomcat instance is running but someone forgot to change the shutdown port settings in server.xml and left it at the default 8005? Or some other process running on that port? netstat *cnn would show you what is running there.

I routinely change all the ports from 80* to something else (search and replace on the 80 and put in 120 or something, stepping through each port setting) so I don't get conflicts across my multiple tomcat installs.

Pete Helgren
Value Added Software, Inc
www.petesworkshop.com
GIAC Secure Software Programmer-Java


On 3/20/2012 12:24 PM, James Lampert wrote:

Anybody know what to make of this?

Here's the scenario: Tomcat 7.0.25 freshly installed on an AS/400
running V6R1. The box has no port restrictions set up in it. The only
ports in use, in the 8000-8099 range are 8000, 8001, 8005, and 8035.

I launch Tomcat, and 8080 and 8009 both open up. Then something connects
to them via loopback. Then the CATALINA job ends (reporting a normal
end), and 8080 and 8009 both close, with connections from Loopback
sitting on the ports until they time out.

HMMMMMmmmmmmm. Looks like Tomcat is trying to open 8005 itself, and
finding it "taken" by something entirely different. What does Tomcat use
8005 for, anyway, and can it be reassigned?