Help Center/ CodeArts Deploy/ FAQs/ Custom Application Actions/ Starting or Stopping Tomcat/ Service Is Not Started Despite Successful Action Deployment

Updated on 2023-05-26 GMT+08:00

View PDF

Service Is Not Started Despite Successful Action Deployment

Symptoms

The command for starting Tomcat is successfully deployed during the deployment of the action Start/Stop Tomcat, but the service is not started.

Cause Analysis

The waiting time is too short. As a result, the service is not started when the waiting time ends.
If the service startup still fails after the waiting time is set to a proper value, check whether the service exits unexpectedly after being started.

Solution

Adjust the waiting time.
Log in to the server where the service is deployed to manually start the service or view logs to locate the service fault.

Parent topic: Starting or Stopping Tomcat

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.