Tomcat faked death.

1 windows 2008 R2 server, started with catlina.bat, but cannot be started after shutdown, indicating that the port is occupied.
2 finds that the port is occupied by java.exe through netstat-an.
3 Task Manager cannot end neither java.exe taskkill nor java.exe taskkill, both of which indicate that no instance is running.

what should I do at this time? do I have to restart the server?

another situation is that the server is particularly prone to false death after running for a period of time. The port is listening, but cannot be accessed, and the login interface can be accessed locally, but cannot be logged in. There is no log output in the background. This happens after
finally shuts down tomcat. -sharp-sharp-sharp problem description

the environmental background of the problems and what methods you have tried

related codes

/ / Please paste the code text below (do not replace the code with pictures)

what result do you expect? What is the error message actually seen?

Mar.30,2021

taskkill this command can carry the process id this parameter, do not know how you call this command will be unable to find the process? The subject can try to find the process of tomcat id and kill it.
in addition, the fake death is likely to be caused by the following problems: 1. The database connection pool is exhausted, causing the acquisition connection to wait all the time, which is actually a deadlock. 2. Because some requests cause the request thread to be occupied and unable to release, it is actually a deadlock. If you encounter a deadlock, you can use jstack to see where the thread is stuck.
refer to here: https://blog.csdn.net/wanglha.


right-click on the cmd title bar after tomcat startup-attribute to remove the quick edit. In addition, tomcat memory is enlarged

Menu