André Warnier wrote: > Mark Thomas wrote: >>> ------- Original Message ------- >>> From: "Xia Guowen" <xi...@leg3s.com> >>> To: "Tomcat Users List" <users@tomcat.apache.org> >>> Sent: 26/06/09, 02:35:58 >>> Subject: Re: Problem of port 8080 >>> >>> I'm so sorry for the first question. >>> >>> My tomcat listen on port 8080, I could access http://server_ip:8080/ >>> everything was ok. >>> # netstat -lnut |grep 80 >>> tcp 0 0 127.0.0.1:8005 >>> 0.0.0.0:* LISTEN >>> tcp 0 0 0.0.0.0:8009 >>> 0.0.0.0:* LISTEN >>> tcp 0 0 :::8080 >>> :::* LISTEN >>> >>> But after running for some time,(uncertain time,2 days or 5 days ) I >>> could't access http://server_ip:8080/. >>> The port 8080 disappeared! >> >> If there is nothing in the Tomcat logs, maybe the linux OOM killer? >> > Mark, > (genuine question here) > Can the OOM Killer kill something tomcat-wise in such a way that ports > 8005 and 8009 would remain listening, but 8080 not ?
I haven't seen any proof that those three ports actually belong to the same process. It is likely, I grant you, since they are the defaults but with re-packaged installs you never know. If those ports are all owned by the same process, no. Something else must be up. Could be IPv6 related but no idea what. Some Tomcat logs would be nice. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
