Xia Guowen wrote:
Those three ports actually belong to the same process.
# netstat -lnutp |grep 80
tcp 0 0 127.0.0.1:8005 0.0.0.0:*
LISTEN 29907/java
tcp 0 0 0.0.0.0:8009 0.0.0.0:*
LISTEN 29907/java
tcp 0 0 0.0.0.0:8080 0.0.0.0:*
LISTEN 29907/java
ipv6 is disable.
Because the coder set up "INFO" level, so the log is too detailed and too big.
When things go wrong, I do not know the specific time.
The issue of randomness, I can not reproduce.
Allright, so what do you want us to do ? Guess ?
Seriously, you could try a few things like :
- a grep on your logfiles for the word "error" or "exception" ?
- change the loglevel
- have some program monitor port 8080 and send you an SMS whenever it is
down (Nagios comes to mind)
- monitor your Tomcat with "top" to see of it is using up increasing
amounts of memory over time
...
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
