Response when Tomcat server startup fails

A note about error handling when starting the Tomcat server. I am training again.

The error that occurred

When restarting the server

Failed to initialize end point associated with ProtocolHandler...

And the message.

It seems that the port numbers were in conflict because I didn't study well and didn't understand.

Coping

I checked the port and PID with netstat -ano according to the material obtained as a result of relying on google teacher.

Apparently the PID 3616 is using 8005, 8009, 8080 ports.

When I checked it with Task Manager, it was caused by javaw.exe. When I finished the task and restarted the server again, it started up safely.

Impressions

In the case of Reference material, it seems that it was in conflict with VMWare related, but in my case I could not shut down the server successfully on eclipse. What is it? (If you think about it, the behavior just before was a little strange.)

There were several ways to deal with it, but there were many patterns that alerted me. This time, only the text appeared on the console, so it was a little difficult to sort out the information.

After all, you should look at the error log properly.

(I also need to study because I simply lack knowledge (even this article is ambiguous (I will do my best)))

reference

JavaEE: Install Tomcat for development (VMware Server Web Access and batting)

Recommended Posts

Response when Tomcat server startup fails
When serialization fails
When the server fails to start in Eclipse
When semantic-ui install fails
Tomcat server settings notes
I checked because the response was strange when debugging with Tomcat 8