By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

Go Live Start carddemo application failed - AWS Mainframe modernization application

0

Go Live Start carddemo application failed. Following is the error from CloudWatch log: com.netfective[ ERROR] 2024-07-02 18:56:06 [main] Catalina - No shutdown port configured. Shut down server through OS signal. Server not shut down.

java.base@11.0.23/java.util.concurrent.locks.LockSupport.park(LockSupport.java:194[ ERROR] 2024-07-02 20:14:42 [main] Catalina - No shutdown port configured. Shut down server through OS signal. Server not shut down.

This looks like error related to Tomcat server.

server.xml has the shutdown port details: <Server port="8005" shutdown="SHUTDOWN"> <Listener className="org.apache.catalina.startup.VersionLoggerListener" />

<!-- Security listener. Documentation at /docs/config/listeners.html <Listener className="org.apache.catalina.security.SecurityListener" /> How this error can be resolved ? Does this port need to be configured anywhere or need to update catalina.properties ? Thanks Praveen
Topics
Migration & Modernization
Tags
AWS Mainframe ModernizationAWS Application Migration ServiceAWS Blu Age
Language
English
Praveen
asked 3 months ago309 views
2 Answers
2
Accepted Answer

Ensure that the port 8005 is available and not being used by another process. You can use tools like netstat to check this. Also, you would not have any firewall rules locking this port.

Is the server.xml readable by Tomcat?

profile picture
EXPERT
Giovanni Lauria
answered 3 months ago
profile picture
EXPERT
Adeleke Adebowale J
reviewed 3 months ago
  • Praveen
    3 months ago

    Thanks for the response.

    The port 8005 is not used by any process and I don't have any firewall rules locking this port. The file server.xml should be readable by Tomcat, but how do I find that if its not accessible by Tomcat or not ?

    Thank you.

  • Giovanni Lauria EXPERT
    3 months ago

    Look at the file permissions.

0

Hello, Were you able to resolve it? I'm facing same issue and unaware how to check anything?

AWS
AWS-User-7948773
answered 2 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content