Unable to open ShipConsole On Prem application and HTTP Status 500 in browser after porting new war file.

Solution: When you see Http 500 which means tomcat is up but there is an issue is either connecting to database or with the war file.

1) Need to verify catalina.out log file for any exceptions.w,r,t java.sql.SQLException: 
Example: javax.naming.NameNotFoundException: or Cannot create PoolableConnectionFactory (Listener refused the connection with the following error: ORA-12505, TNS:listener does not currently know of SID given in connect descriptor) 

In this Scenario DBA's need to validate Tomcat/Conf/context.xml file and validate JDBC connection URL and also username and password details. Correct if neccessary and then restart the tomcat.

   
    2) Report to ShipConsole Support for validation by sharing ShipConsole.log and catalina.out log from Tomcat/logs/ directory.