Blogged 8005 port explanation: server. XML
< Server port = "8005" shutdown "> shutdown ="
Startup log:
SEVERE: StandardServer await: create [j]] : - 8005 display unable to create this 8005 port
Java.net. BindException: can they requested does
At Java.net. PlainSocketImpl socketBind (of) Native.
At Java.net. PlainSocketImpl. Bind (PlainSocketImpl. Java: 365)
At Java.net. ServerSocket. Bind (ServerSocket. Java: 319)
At Java.net. ServerSocket. < > (init ServerSocket. Java: 185)
Org. I can with apache mig-at catalina. J j j j core StandardServer await (j) 373 StandardServer Java:
Org. I can with apache catalina at startup. J j catalina. Await (catalina. Java: 662)
Org. I can with apache catalina at startup. J j catalina. Start (catalina. Java: 614)
At NativeMethodAccessorImpl reflect. J from invoke0 (Native) of.
At NativeMethodAccessorImpl. J j j reflect from invoke (NativeMethodAccessorImpl. Java: 39),
At DelegatingMethodAccessorImpl. J j j reflect from invoke (25) DelegatingMethodAccessorImpl. Java:
At Java. J j j j well reflect of invoke (of Java: 5.97).
Org. I can with apache mig-at catalina. J j j startup Bootstrap. Start (Bootstrap. Java: 289)
Org. I can with apache mig-at catalina. J j j j startup Bootstrap main (Bootstrap. Java: 414)
By 2010, Aug 6 11:12:15 AM org. I can with apache coyote. J j http11 Http11Protocol pause
Results-related areas: Pausing Coyote HTTP / 1.1 on HTTP - 8082
By 2010, Aug 6 11:12:16 AM org. I can with apache catalina. J j core StandardService stop
Results-related areas: Stopping service Catalina
The result is caused tomcat failed to start, fail to start
The first step judgment: port occupation
An grep netstat - | 8005 no results
That since no port occupy words, what was the question?
In view of time constraints, and the server only one application deployment, so he decided to restart server, look to whether problem remains
The second step restart server, results fault remains
So, the question is not simple port occupied, there may be more troublesome things
Because this project has been running for a long time, is unlikely to be some low-level problem
Then, because it is less tomcat, configuration files, then check configuration file server. XML it
Check after, not found any abnormal ah.
So see whether can find the answer on the network, searched next, still can 8005 port, the reason is the port, belong to Localhost
Not bound to a designated IP address, if the server ping localhost words, so sure that's the problem
So the ping localhost result was said, I cannot find this host
, found the problem
So in/etc/hosts file added a record
127.0.0.1 localhost
And then restart tomcat, problem solving.
The following are server hosts file, everybody can see next:
More/etc/hosts
This is my 127.0.0.1 localhost # machine added
127.0.0.1 localhost. Localdomain localhost
192.168.11.100 localhost. Localdomain localhost
: : 1 localhost6
Dec 9, 2010
Tomcat fault handling - port problem
editor
tom
/ On : 12/09/2010/ Thank you for visiting my small blog here. If you wanted to discuss or have the question around this article, please contact me e-mail at herdiansyah hamzah@yahoo.com.