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.
Related
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.
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.
Following are the startup log messages:
Check if Algo ant logger exists
Found Algo logger, starting with Algo ant logging
Buildfile: $ALGOWEBAPPS_HOME/bin/algowebapps-control.xml
Deleting:$ALGO_TOP/algowebapps/webapps/
acm.war,acm470help.war,awl.war,dmcfg.war,Navigator.war,mdc.war,Visualizer.war
Copying 7 file to $ALGO_TOP/algowebapps/webapps
Deleting directory $ALGO_TOP/algowebapps/webapps/awl
Copying 1 file to $ALGO_TOP/algowebapps/webapps/ROOT
Sep 26, 2017 10:18:25 PM 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...
Sep 26, 2017 10:18:25 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-12001
Sep 26, 2017 10:18:26 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8888
Sep 26, 2017 10:18:26 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1145 ms
Sep 26, 2017 10:18:26 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Sep 26, 2017 10:18:26 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.32
Sep 26, 2017 10:18:26 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive Navigator.war
Load details in $ALGO_TOP/algowebapps/webapps/Navigator//MetaTables.xml
Loaded 11 tables & views
Load details of db jdbc:oracle:thin:#UAT4
Load details of db jdbc:oracle:thin:#UAT4
Sep 26, 2017 10:18:32 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive mdc.war
Sep 26, 2017 10:18:32 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive acm.war
INFO: GridServlet - ==> initializing GridServlet processing
INFO: TreeServlet - ==> initializing TreeServlet processing
==> initializing LoaderServlet
INFO: AjaxStoreServlet - ==> initializing AjaxStoreServlet processing
INFO: ConfigStoreServlet - ==> initializing ConfigStoreServlet processing
INFO: ActionDataServlet - ==> initializing Ricos HTTP Servlet Executer
INFO: ExecuterServlet2 - ==> initializing Ricos HTTP Servlet Executer
INFO: ValidationServlet - ==> initializing ValidationServlet processing
Sep 26, 2017 10:18:32 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive acm470help.war
Sep 26, 2017 10:18:32 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive awl.war
Sep 26, 2017 10:18:32 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive dmcfg.war
2017-09-26 22:18:33,525 DEBUG [dmcfg] Installing into composite=com.algorithmics.log.provider.DailyLogFileProvider com.algorithmics.log.provider.CompositeLogProvider
2017-09-26 22:18:33,533 DEBUG [dmcfg] File path 'log' is relative - prepending ALGO_TOP=/opt/bns/alreu4/Algo/ALGO_TOP com.algorithmics.log.provider.DailyLogFileProvider
2017-09-26 22:18:33,534 DEBUG [dmcfg] Opening file '$ALGO_TOP/log/dmcfg-default-sbuvvrwm471-2017-09-26.log' om.algorithmics.log.provider.DailyLogFileProvider
2017-09-26 22:18:33,541 DEBUG [dmcfg] Installing into composite=com.algorithmics.log.provider.ConsoleLogProvider com.algorithmics.log.provider.CompositeLogProvider
Sep 26, 2017 10:18:36 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive Visualizer.war
Initializing started...
<<<It hangs here indefinitely>>>
Below is what is expected to follow in a normal startup:
[[
Initializing finished...
Sep 26, 2017 10:37:48 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory ROOT
Sep 26, 2017 10:37:48 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-12001
Sep 26, 2017 10:37:48 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8443
Sep 26, 2017 10:37:48 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 7637 ms
]]
Is downloading Tomcat cource code and enable Tomcat debug mode the only choice to identify the root cause of such issue? But I have no access to the source code of those applications running in Tomcat (I can decompile the jar files in war files though it's a tedious). or there might be better way to figure out the cause?
This seems to be an issue with the deployed application start up. You would have to enable debug logging for the application and see the root cause.
You might also check the context.xml for the webapp and see if it's connecting to an external resource, e.g., a database. The log message explicitly mentions an Oracle jdbc driver, it may be hanging while trying to create a database connection pool.
the problem is now mitigated by a upgrade of NFS server to V4.
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 7 years ago.
Improve this question
Each time i make a new project and run it i get error not found
and here is the console log :
Sep 10, 2015 11:58:31 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: C:\Program Files\Java\jre1.8.0_60\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:/Program Files/Java/jre1.8.0_60/bin/client;C:/Program Files/Java/jre1.8.0_60/bin;C:/Program Files/Java/jre1.8.0_60/lib/i386;C:\ProgramData\Oracle\Java\javapath;C:\oracle\ora92\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files\Seagate Software\NOTES\;C:\Program Files\Seagate Software\NOTES\DATA\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;F:\Sources\eclipse;;.
Sep 10, 2015 11:58:31 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
Sep 10, 2015 11:58:31 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
Sep 10, 2015 11:58:31 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1545 ms
Sep 10, 2015 11:58:31 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Sep 10, 2015 11:58:31 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.64
Sep 10, 2015 11:58:32 AM org.apache.catalina.util.SessionIdGeneratorBase createSecureRandom
INFO: Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [156] milliseconds.
Sep 10, 2015 11:58:32 AM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor F:\Java projects\.metadata\.plugins\org.eclipse.wst.server.core\tmp1\conf\Catalina\localhost\Courses.xml
Sep 10, 2015 11:58:32 AM org.apache.catalina.startup.SetContextPropertiesRule begin
WARNING: [SetContextPropertiesRule]{Context} Setting property 'source' to 'org.eclipse.jst.jee.server:Courses' did not find a matching property.
Sep 10, 2015 11:58:36 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.
Sep 10, 2015 11:58:36 AM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deployment of configuration descriptor F:\Java projects\.metadata\.plugins\org.eclipse.wst.server.core\tmp1\conf\Catalina\localhost\Courses.xml has finished in 3,819 ms
Sep 10, 2015 11:58:36 AM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor F:\Java projects\.metadata\.plugins\org.eclipse.wst.server.core\tmp1\conf\Catalina\localhost\CoursesPro.xml
Sep 10, 2015 11:58:36 AM org.apache.catalina.startup.SetContextPropertiesRule begin
WARNING: [SetContextPropertiesRule]{Context} Setting property 'source' to 'org.eclipse.jst.jee.server:CoursesPro' did not find a matching property.
Sep 10, 2015 11:58:36 AM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deployment of configuration descriptor F:\Java projects\.metadata\.plugins\org.eclipse.wst.server.core\tmp1\conf\Catalina\localhost\CoursesPro.xml has finished in 33 ms
Sep 10, 2015 11:58:36 AM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor F:\Java projects\.metadata\.plugins\org.eclipse.wst.server.core\tmp1\conf\Catalina\localhost\CoursesTest.xml
Sep 10, 2015 11:58:36 AM org.apache.catalina.startup.SetContextPropertiesRule begin
WARNING: [SetContextPropertiesRule]{Context} Setting property 'source' to 'org.eclipse.jst.jee.server:CoursesTest' did not find a matching property.
Sep 10, 2015 11:58:37 AM org.apache.catalina.loader.WebappClassLoader validateJarFile
INFO: validateJarFile(F:\Java projects\.metadata\.plugins\org.eclipse.wst.server.core\tmp1\wtpwebapps\CoursesTest\WEB-INF\lib\javax.servlet-api-3.0.1.jar) - jar not loaded. See Servlet Spec 3.0, section 10.7.2. Offending class: javax/servlet/Servlet.class
Sep 10, 2015 11:58:39 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.
Sep 10, 2015 11:58:39 AM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deployment of configuration descriptor F:\Java projects\.metadata\.plugins\org.eclipse.wst.server.core\tmp1\conf\Catalina\localhost\CoursesTest.xml has finished in 3,721 ms
Sep 10, 2015 11:58:39 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8080"]
Sep 10, 2015 11:58:39 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-bio-8009"]
Sep 10, 2015 11:58:39 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 8231 ms**
You're deploying on tomcat. The default things to check are:
is your application displayed as 'running' in the manager
If displayed as failed, it failed, and there should be something in the logs. Probably your logging is misconfigured.
If not even displayed, you don't have a web.xml or context.xml file
does your application look sane in the deploy directory
According to your logs it's at F:\Java projects\.metadata\.plugins\org.eclipse.wst.server.core\tmp1\wtpwebapps\CoursesTest. Check there if WEB-INF/web.xml is present, and if the file that you're trying to reach is actually in that folder.
are you using a correct url?
If you're just trying to open the root url of your application, and there is no index or default servlet to handle it, you can get this error. Other urls might work though.
*
I have configured Tomcat 7 with Eclipse Helios 1.3.2 on port number 8080. Tomcat Service and everything is installed.
When I am starting the server from Eclipse, it does some process and shows the status as STARTED. But when I try to hit http://localhost:8080, it says The requested resource (/) is not available. i.e. in fact server is not started in reality.
However, when I am starting the server from Windows Explorer by running Tomcat7.exe or Tomcat7w.exe, it starts well and I am able to see Apache Home page by referring to http://localhost:8080.
Below is the server start up log.
Jul 02, 2012 1:20:12 PM 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: C:\Program Files\Java\jre7\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:/Program Files/Java/jre7/bin/client;C:/Program Files/Java/jre7/bin;C:/Program Files/Java/jre7/lib/i386;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Perforce;O:\ora1106w\bin;C:\Program Files\Java\jdk1.6.0_12\bin;;C:\Program Files\WinMerge;C:\Users\KNIRAV\Downloads\eclipse-jee-helios-SR2-win32\eclipse;;.
Jul 02, 2012 1:20:17 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
Jul 02, 2012 1:20:17 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
Jul 02, 2012 1:20:17 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 5674 ms
Jul 02, 2012 1:20:17 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Jul 02, 2012 1:20:17 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.28
Jul 02, 2012 1:20:18 PM org.apache.catalina.util.SessionIdGenerator createSecureRandom
INFO: Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [126] milliseconds.
Jul 02, 2012 1:20:18 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8080"]
Jul 02, 2012 1:20:18 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-bio-8009"]
Jul 02, 2012 1:20:18 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 1788 ms
Can I have some solution to this please?
There is no problem. When you start Tomcat from Eclipse a root application is not deployed. Only the projects that you deploy through the server view are available.
Have you tried to deploy a project on the server?