Spring Boot Can Still Be Detected After Being Stopped (on Windows)
Symptoms
The command for stopping Spring Boot is successfully deployed during the deployment of the action Start/Stop Spring Boot, but the Spring Boot process can still be detected.
Cause Analysis
Spring Boot in the current path is registered as a Windows service and the startup mode is automatic startup.
Solution
- Run the following command to open the Windows service list:
services.msc
- Search for service names similar to devployMan_SpringBoot_01-0.0.1-SNAPSHOT.jar.
If a similar service name exists, run the following two commands in sequence:
nssm stop devployMan_SpringBoot_01-0.0.1-SNAPSHOT.jar nssm remove devployMan_SpringBoot_01-0.0.1-SNAPSHOT.jar
Starting or Stopping Spring Boot FAQs
- Invalid Spring Boot Path
- Startup Failed
- Environment Variables Are Not Configured
- Service Is Not Started Despite Successful Action Deployment
- Spring Boot Can Still Be Detected After Being Stopped (on Windows)
- Instruction
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore