On 12/07/2011 16:15, David Brown wrote: > Hello, I have found a situation that kills tc on startup within about 3 > seconds on a 64-bit cloud running Ubuntu server. localhost resolves > correctly via dig but if we ping localhost it resolves to localhost.com. > this in my estimation is causing tc to bail. the tc 7 installed is 64 > with a sun-oracle 64 bit jdk all fresh out-of-the-box with no config or > changes. This is a vulnerability in my estimation unless somebody can > prove different.
Tomcat failing to start because of incorrectly configured networking at the OS level is not a vulnerability. Fix the network configuration and the problem will go away. > catalina.out only shows the 8005 port exception unable to bind to 8005 > on localhost. i have already run all the possible tests for previous > version of tc running or some other process or daemon attached to 8005. > There are no other instances on the system and tc could not have > previously been running since this was a new out-of-the-box install with > no changes. The, on startup the tc 7 instance dies immediately (about 3 > sec.) with only the same 8005 exception in the logs. > > Is it possible to define some other ip than 127.0.0.1 to use for 8005? > > Pls advise. Read the docs for the server element. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
