Develop Reference

Tomcat 404 error not serving Java webapp when running eclipse

I've been struggling for 1 month and multiple employees at my company have come across the same issue. Whenever I run my java project on eclipse using Apache Tomcat and open it in my chrome browser, it shows a 404 error. After multiple reinstalls, when I open localhost, tomcat doesn't even work, now I only receive the Chrome default error message: "The site can't be reached".
Below is a snippet of the logs I receive when I startup my tomcat 7.0 server -->
INFO: Command line argument: -Dfile.encoding=Cp1252
Jun 08, 2021 3:24:43 PM org.apache.catalina.core.AprLifecycleListener lifecycleEvent
INFO: The Apache Tomcat Native library which allows using OpenSSL was not found on the java.library.path: [C:\Program Files\Java\jre1.8.0_291\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:/Program Files/Java/jre1.8.0_291/bin/server;C:/Program Files/Java/jre1.8.0_291/bin;C:/Program Files/Java/jre1.8.0_291/lib/amd64;C:\Program Files (x86)\Razer\ChromaBroadcast\bin;C:\Program Files\Razer\ChromaBroadcast\bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Program Files\AdoptOpenJDK\jdk-11.0.8.10-hotspot\bin;C:\Program Files\AdoptOpenJDK\jdk-14.0.2.12-hotspot\bin;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\nodejs\;C:\Users\akpme\AppData\Local\Microsoft\WindowsApps;C:\Program Files\JetBrains\PyCharm Community Edition 2019.2.3\bin;C:\ProgramData\akpme\atom\bin;C:\Users\akpme\AppData\Local\Microsoft\WindowsApps;C:\Users\akpme\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\akpme\AppData\Roaming\npm;C:\Program Files\heroku\bin;C:\cmake\cmake-3.19.2-win64-x64\bin;C:\Users\akpme\AppData\Local\Programs\Python\Python37;C:\Users\akpme\AppData\Local\Programs\Python\Python37\python.exe;C:\Users\akpme\AppData\Local\Programs\Python\Python37\python3.7.exe;C:\Program Files\Git\cmd;C:\Program Files (x86)\Microsoft SQL Server\150\DTS\Binn\;C:\Program Files\Azure Data Studio\bin;C:\Program Files\PuTTY\;C:\Users\akpme\.windows-build-tools\python27\;C:\Users\akpme\AppData\Local\Microsoft\WindowsApps;C:\Program Files\JetBrains\PyCharm Community Edition 2019.2.3\bin;C:\ProgramData\akpme\atom\bin;C:\Users\akpme\AppData\Local\Microsoft\WindowsApps;C:\Users\akpme\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\akpme\AppData\Roaming\npm;C:\Program Files\heroku\bin;C:\Users\akpme\AppData\Local\GitHubDesktop\bin;C:\Program Files\Azure Data Studio\bin;C:\Programming\SaveAway\eclipse;;.]
Jun 08, 2021 3:24:44 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8090"]
Jun 08, 2021 3:24:44 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1785 ms
Jun 08, 2021 3:24:44 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service [Catalina]
Jun 08, 2021 3:24:44 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.107
Jun 08, 2021 3:24:45 PM org.apache.catalina.loader.WebappClassLoaderBase validateJarFile
INFO: validateJarFile(C:\Users\akpme\eclipse-workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\wtpwebapps\InSpirAVE\WEB-INF\lib\servlet-api.jar) - jar not loaded. See Servlet Spec 3.0, section 10.7.2. Offending class: javax/servlet/Servlet.class
Jun 08, 2021 3:24:59 PM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Jun 08, 2021 3:24:59 PM org.apache.catalina.core.ApplicationContext log
INFO: No Spring WebApplicationInitializer types detected on classpath
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/C:/Users/akpme/eclipse-workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/InSpirAVE/WEB-INF/lib/slf4j-log4j12-1.7.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/C:/Users/akpme/eclipse-workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/InSpirAVE/WEB-INF/lib/slf4j-log4j12-1.7.7.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console.
Jun 08, 2021 3:25:00 PM org.apache.catalina.core.ApplicationContext log
INFO: Initializing Spring root WebApplicationContext
Jun 08, 2021 3:25:06 PM org.apache.catalina.util.SessionIdGeneratorBase createSecureRandom
WARNING: Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [409] milliseconds.
Jun 08, 2021 3:25:06 PM org.apache.catalina.core.ApplicationContext log
INFO: Initializing Spring FrameworkServlet 'mvc-dispatcher'
Jun 08, 2021 3:25:06 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8090"]
Jun 08, 2021 3:25:06 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 22419 ms
===========================================================================
Chrome Browser Screen:
==========================================================================
If you need anything else please email me at mahit.py#gmail.com.

Tomcat: One or more listeners failed to start

I have an application which is not starting up after I added/upgraded some dependencies. It logs an error saying
SEVERE: One or more listeners failed to start. Full details will be found in the appropriate container log file
I saw all the log files, and catalina., localhost., application.*, but none of them seem to have the stacktrace because of which the startup is breaking.
This is tomcat8, java8.
How do I check the logs and where can the logs go other than the normal tomcat folder.
Catalina logs:
Feb 06, 2018 3:07:32 PM org.apache.catalina.core.AprLifecycleListener lifecycleEvent
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: [
/user/name/Library/Java/Extensions:/Library/Java/Extensions:/Network/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java:.]
Feb 06, 2018 3:07:32 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-nio-7060"]
Feb 06, 2018 3:07:32 PM org.apache.tomcat.util.net.NioSelectorPool getSharedSelector
INFO: Using a shared selector for servlet write/read
Feb 06, 2018 3:07:32 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-nio-9060"]
Feb 06, 2018 3:07:32 PM org.apache.tomcat.util.net.NioSelectorPool getSharedSelector
INFO: Using a shared selector for servlet write/read
Feb 06, 2018 3:07:32 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 556 ms
Feb 06, 2018 3:07:32 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service [Catalina]
Feb 06, 2018 3:07:32 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/8.5.23
Feb 06, 2018 3:07:32 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive [/usr/local/Cellar/tomcat/8.5.23/libexec/webapps/application.war]
Feb 06, 2018 3:07:48 PM org.apache.jasper.servlet.TldScanner scanJars
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Feb 06, 2018 3:08:07 PM redis.clients.jedis.JedisSentinelPool initSentinels
INFO: Trying to find master from available Sentinels...
Feb 06, 2018 3:08:07 PM redis.clients.jedis.JedisSentinelPool initSentinels
INFO: Redis master running at 127.0.0.1:6379, starting Sentinel listeners...
Feb 06, 2018 3:08:07 PM redis.clients.jedis.JedisSentinelPool initPool
INFO: Created JedisPool to master at 127.0.0.1:6379
Hibernate: A complicated Hibernate query
Feb 06, 2018 3:08:25 PM com.sun.faces.config.ConfigureListener contextInitialized
INFO: Initializing Mojarra 2.2.7 ( 20140610-1547 https://svn.java.net/svn/mojarra~svn/tags/2.2.7#13362) for context '/application'
Feb 06, 2018 3:08:25 PM com.sun.faces.spi.InjectionProviderFactory createInstance
INFO: JSF1048: PostConstruct/PreDestroy annotations present. ManagedBeans methods marked with these annotations will have said annotations processed.
Feb 06, 2018 3:08:26 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deployment of web application archive [/usr/local/Cellar/tomcat/8.5.23/libexec/webapps/application.war] has finished in [53,864] ms
Feb 06, 2018 3:08:26 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory [/usr/local/Cellar/tomcat/8.5.23/libexec/webapps/docs]
Feb 06, 2018 3:08:26 PM org.apache.jasper.servlet.TldScanner scanJars
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Feb 06, 2018 3:08:26 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory [/usr/local/Cellar/tomcat/8.5.23/libexec/webapps/docs] has finished in [386] ms
Feb 06, 2018 3:08:26 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory [/usr/local/Cellar/tomcat/8.5.23/libexec/webapps/examples]
Feb 06, 2018 3:08:27 PM org.apache.jasper.servlet.TldScanner scanJars
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Feb 06, 2018 3:08:27 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory [/usr/local/Cellar/tomcat/8.5.23/libexec/webapps/examples] has finished in [551] ms
Feb 06, 2018 3:08:27 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory [/usr/local/Cellar/tomcat/8.5.23/libexec/webapps/host-manager]
Feb 06, 2018 3:08:27 PM org.apache.jasper.servlet.TldScanner scanJars
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Feb 06, 2018 3:08:27 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory [/usr/local/Cellar/tomcat/8.5.23/libexec/webapps/host-manager] has finished in [363] ms
Feb 06, 2018 3:08:27 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory [/usr/local/Cellar/tomcat/8.5.23/libexec/webapps/manager]
Feb 06, 2018 3:08:28 PM org.apache.jasper.servlet.TldScanner scanJars
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Feb 06, 2018 3:08:28 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory [/usr/local/Cellar/tomcat/8.5.23/libexec/webapps/manager] has finished in [295] ms
Feb 06, 2018 3:08:28 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory [/usr/local/Cellar/tomcat/8.5.23/libexec/webapps/ROOT]
Feb 06, 2018 3:08:28 PM org.apache.jasper.servlet.TldScanner scanJars
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Feb 06, 2018 3:08:28 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory [/usr/local/Cellar/tomcat/8.5.23/libexec/webapps/ROOT] has finished in [298] ms
Feb 06, 2018 3:08:28 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-nio-7060"]
Feb 06, 2018 3:08:28 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-nio-9060"]
Feb 06, 2018 3:08:28 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 55840 ms

Found a simple way to identify the problem.
In your WEB-INF/classes directory of the application, make a new file: logging.properties.
Add the following in that file:
org.apache.catalina.core.ContainerBase.[Catalina].level=INFO
org.apache.catalina.core.ContainerBase.[Catalina].handlers=java.util.logging.ConsoleHandler
Restart tomcat.
Now you'll have the complete stacktrace and debug the problem from there on.
For a Maven Build
Create a new logging.properties in the src/main/resources directory of the module
Add these entries into that new file
org.apache.catalina.core.ContainerBase.[Catalina].level=INFO
org.apache.catalina.core.ContainerBase.[Catalina].handlers=java.util.logging.ConsoleHandler
Run mvn clean install
Restart Tomcat

Adding the logging.properties file didn't do anything for me. Instead found the stack trace of my error in tomcat/logs/localhost.[YYYY-MM-DD].log.

This helped to find the error log file and the actual error
sh bin/startup.sh ; tail -f logs/*.log;

In my case, i found logs in localhost.log file located in Tomcat_Home/logs. Wish this help u.

Tomcat 7: One or more listeners failed to start

My war file on Tomcat is failing to start. Not sure where to go from here. Below is the output of catalina.log on a restart. I see the javax.servlet-api-3.1.0.jar error, but I don't think that would prevent the war from starting. Can someone help me out? Thanks!
Jun 14, 2017 9:47:25 AM org.apache.catalina.core.StandardServer await
INFO: A valid shutdown command was received via the shutdown port. Stopping the Server instance.
Jun 14, 2017 9:47:25 AM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["http-bio-8080"]
Jun 14, 2017 9:47:30 AM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["http-bio-8443"]
Jun 14, 2017 9:47:30 AM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["ajp-bio-8009"]
Jun 14, 2017 9:47:30 AM org.apache.catalina.core.StandardService stopInternal
INFO: Stopping service Catalina
Jun 14, 2017 9:48:27 AM org.apache.catalina.startup.SetAllPropertiesRule begin
WARNING: [SetAllPropertiesRule]{Server/Service/Connector} Setting property 'maxSpareThreads' to '75' did not find a matching property.
Jun 14, 2017 9:48:27 AM org.apache.catalina.startup.VersionLoggerListener log
INFO: Server version: Apache Tomcat/7.0.77
Jun 14, 2017 9:48:27 AM org.apache.catalina.startup.VersionLoggerListener log
INFO: Server built: Mar 28 2017 16:01:48 UTC
Jun 14, 2017 9:48:27 AM org.apache.catalina.startup.VersionLoggerListener log
INFO: Server number: 7.0.77.0
Jun 14, 2017 9:48:27 AM org.apache.catalina.startup.VersionLoggerListener log
INFO: OS Name: Linux
Jun 14, 2017 9:48:27 AM org.apache.catalina.startup.VersionLoggerListener log
INFO: OS Version: 4.1.12-94.3.4.el6uek.x86_64
Jun 14, 2017 9:48:27 AM org.apache.catalina.startup.VersionLoggerListener log
INFO: Architecture: amd64
Jun 14, 2017 9:48:27 AM org.apache.catalina.startup.VersionLoggerListener log
INFO: Java Home: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.41.x86_64/jre
Jun 14, 2017 9:48:27 AM org.apache.catalina.startup.VersionLoggerListener log
INFO: JVM Version: 1.6.0_41-b41
Jun 14, 2017 9:48:27 AM org.apache.catalina.startup.VersionLoggerListener log
INFO: JVM Vendor: Sun Microsystems Inc.
Jun 14, 2017 9:48:27 AM org.apache.catalina.startup.VersionLoggerListener log
INFO: CATALINA_BASE: /opt/apache-tomcat-7.0.77
Jun 14, 2017 9:48:27 AM org.apache.catalina.startup.VersionLoggerListener log
INFO: CATALINA_HOME: /opt/apache-tomcat-7.0.77
Jun 14, 2017 9:48:27 AM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Djava.util.logging.config.file=/opt/apache-tomcat-7.0.77/conf/logging.properties
Jun 14, 2017 9:48:27 AM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
Jun 14, 2017 9:48:27 AM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Djdk.tls.ephemeralDHKeySize=2048
Jun 14, 2017 9:48:27 AM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Djava.endorsed.dirs=/opt/apache-tomcat-7.0.77/endorsed
Jun 14, 2017 9:48:27 AM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Dcatalina.base=/opt/apache-tomcat-7.0.77
Jun 14, 2017 9:48:27 AM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Dcatalina.home=/opt/apache-tomcat-7.0.77
Jun 14, 2017 9:48:27 AM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Djava.io.tmpdir=/opt/apache-tomcat-7.0.77/temp
Jun 14, 2017 9:48:27 AM org.apache.catalina.core.AprLifecycleListener lifecycleEvent
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
Jun 14, 2017 9:48:28 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
Jun 14, 2017 9:48:28 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8443"]
Jun 14, 2017 9:48:28 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
Jun 14, 2017 9:48:28 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 2785 ms
Jun 14, 2017 9:48:29 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Jun 14, 2017 9:48:29 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.77
Jun 14, 2017 9:48:29 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive /opt/apache-tomcat-7.0.77/webapps/StudentPlanner-war-4.1.5.war
Jun 14, 2017 9:48:36 AM org.apache.catalina.loader.WebappClassLoaderBase validateJarFile
INFO: validateJarFile(/opt/apache-tomcat-7.0.77/webapps/StudentPlanner-war-4.1.5/WEB-INF/lib/javax.servlet-api-3.1.0.jar) - jar not loaded. See Servlet Spec 3.0, section 10.7.2. Offending class: javax/servlet/Servlet.class
Jun 14, 2017 9:48:49 AM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Jun 14, 2017 9:48:51 AM org.apache.catalina.core.StandardContext startInternal
SEVERE: One or more listeners failed to start. Full details will be found in the appropriate container log file
Jun 14, 2017 9:48:51 AM org.apache.catalina.core.StandardContext startInternal
SEVERE: Context [/StudentPlanner-war-4.1.5] startup failed due to previous errors
Jun 14, 2017 9:48:51 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deployment of web application archive /opt/apache-tomcat-7.0.77/webapps/StudentPlanner-war-4.1.5.war has finished in 22,728 ms
Jun 14, 2017 9:48:51 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /opt/apache-tomcat-7.0.77/webapps/host-manager
Jun 14, 2017 9:48:52 AM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Jun 14, 2017 9:48:52 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory /opt/apache-tomcat-7.0.77/webapps/host-manager has finished in 388 ms
Jun 14, 2017 9:48:52 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /opt/apache-tomcat-7.0.77/webapps/ROOT
Jun 14, 2017 9:48:52 AM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Jun 14, 2017 9:48:52 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory /opt/apache-tomcat-7.0.77/webapps/ROOT has finished in 235 ms
Jun 14, 2017 9:48:52 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /opt/apache-tomcat-7.0.77/webapps/docs
Jun 14, 2017 9:48:52 AM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Jun 14, 2017 9:48:52 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory /opt/apache-tomcat-7.0.77/webapps/docs has finished in 156 ms
Jun 14, 2017 9:48:52 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /opt/apache-tomcat-7.0.77/webapps/manager
Jun 14, 2017 9:48:52 AM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Jun 14, 2017 9:48:52 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory /opt/apache-tomcat-7.0.77/webapps/manager has finished in 210 ms
Jun 14, 2017 9:48:52 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /opt/apache-tomcat-7.0.77/webapps/examples
Jun 14, 2017 9:48:54 AM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Jun 14, 2017 9:48:54 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory /opt/apache-tomcat-7.0.77/webapps/examples has finished in 1,768 ms
Jun 14, 2017 9:48:54 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8080"]
Jun 14, 2017 9:48:54 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8443"]
Jun 14, 2017 9:48:54 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-bio-8009"]
Jun 14, 2017 9:48:54 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 25801 ms

In my case, there are many tomcat as well as jdk versions configured on my system. Issue is resolved when I deleted system level environment variables CATALINA_HOME and JAVA_HOME and set them at user level as per deployment need.

Is there any possibility to see logs of *.war file execution?

I started my web application using
java $JAVA_OPTS -jar target/dependency/webapp-runner.jar --port 9000 *.war
Is there any way to see logs now?
My console output:
sergei_rudenkov#EPAm18851:~/IdeaProjects/fsdf$ java $JAVA_OPTS -jar target/dependency/webapp-runner.jar --port 9000 web-archive-test.war
Adding Context for web-archive-test.war
Feb 05, 2016 2:18:33 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-nio-9000"]
Feb 05, 2016 2:18:33 PM org.apache.tomcat.util.net.NioSelectorPool getSharedSelector
INFO: Using a shared selector for servlet write/read
Feb 05, 2016 2:18:33 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Tomcat
Feb 05, 2016 2:18:33 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/8.0.24
Feb 05, 2016 2:18:33 PM org.apache.catalina.startup.ContextConfig getDefaultWebXmlFragment
INFO: No global web.xml found
Feb 05, 2016 2:18:33 PM org.apache.jasper.servlet.TldScanner scanJars
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Feb 05, 2016 2:18:33 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-nio-9000"]
My browser:
I has logging.file=mylog.log in application.properties but it doesn't write anything.
I created war file using this command jar cvf web-archive-test.war .
What is interesting everything works fine when I launch it from Idea.

You implemented a logging system?
NO: go to C:\Program Files\Apache Software Foundation\Tomcat x.x\logs to find them
YES
You provided a specific log folder in config?
YES search for this folder location in the server filesystem.
NO search for the default log folder of your logging system.

Unable to connect to tomcat7

I deployed a new version of a .war file and the tomcat7 is also running fine as status shows me:
root#s17298254:/var/lib/tomcat7/webapps# service tomcat7 status
* Tomcat servlet engine is running with pid 11331
Now the question is that neither I am able to view the website, nor I am able to view the manager interface in my web browser. Please note that its in production environment that I am using this tomcat instance. What could be the reason?
I have tried many things like running tomcat as root user previlages(although a disaster recepie, but atleast to make things work temporarily), putting
useIPVHosts="true"
under <Connector> etc.
Here is my catalina.out:
Mar 12, 2014 7:04:24 AM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64/server:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64:/usr/lib/jvm/java-6-openjdk-amd64/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib/x86_64-linux-gnu/jni:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/usr/lib/jni:/lib:/usr/lib
Mar 12, 2014 7:04:25 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting property 'xmlValidation' to 'false' did not find a matching property.
Mar 12, 2014 7:04:25 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting property 'xmlNamespaceAware' to 'false' did not find a matching property.
Mar 12, 2014 7:04:25 AM org.apache.tomcat.util.digester.Digester endElement
WARNING: No rules found matching 'Server/Service/Engine/Host/Logger'.
Mar 12, 2014 7:04:25 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-80"]
Mar 12, 2014 7:04:25 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
Mar 12, 2014 7:04:25 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 2038 ms
Mar 12, 2014 7:04:25 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Mar 12, 2014 7:04:25 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.26
Mar 12, 2014 7:04:26 AM org.apache.catalina.loader.WebappClassLoader validateJarFile
INFO: validateJarFile(/var/lib/tomcat7/webapps/camriders/WEB-INF/lib/servlet-api-2.5.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
Mar 12, 2014 7:04:27 AM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://www.springframework.org/tags is already defined
Mar 12, 2014 7:04:31 AM org.apache.catalina.core.ApplicationContext log
INFO: Initializing Spring root WebApplicationContext
It does not show me anything pathogenic.So what could be the cause that my website is now no longer working?
EDIT:
The error when i type in browser mywebsite.mydomain.net is:
Firefox can't establish a connection to the server at mywebsite.mydomain.net.
Similar with google chrome.

In tomcat 7 use 'xmlValidation' and 'xmlNamespaceAware' under context element.
<Context path="" docBase="ROOT" xmlValidation="false" xmlNamespaceAware="false"/>