mtrehans Posted January 19, 2017 Share Posted January 19, 2017 Apache Tomcat8 Service is not starting.Under Apache Tomcate8 -->Properties--> Java Tab below are the Java options added:Dcatalina.home=C:Program Filesapache-tomcat-8.0.33-windows-x64apache-tomcat-8.0.33-Dcatalina.base=C:Program Filesapache-tomcat-8.0.33-windows-x64apache-tomcat-8.0.33-Djava.endorsed.dirs=C:Program Filesapache-tomcat-8.0.33-windows-x64apache-tomcat-8.0.33endorsed-Djava.io.tmpdir=C:Program Filesapache-tomcat-8.0.33-windows-x64apache-tomcat-8.0.33temp-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager-Djava.util.logging.config.file=C:Program Filesapache-tomcat-8.0.33-windows-x64apache-tomcat-8.0.33conflogging.properties-XX:PermSize=32m-XX:+UseConcMarkSweepGC-XX:+CMSClassUnloadingEnabled-XX:MaxPermSize=512m-Djs.license.directory=C:Program Filesapache-tomcat-8.0.33-windows-x64apache-tomcat-8.0.33webappsjasperserver-pro Where Initial memory pool set to : 4096Maximum memory pool set to : 6144Thread stack size set to : 6144 Attached is the log file of "tomcat8-stderr.2017-01-19" 2017-01-19 01:37:15 Commons Daemon procrun stderr initialized19-Jan-2017 01:37:15.881 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version: Apache Tomcat/8.0.3319-Jan-2017 01:37:15.883 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built: Mar 18 2016 20:31:49 UTC19-Jan-2017 01:37:15.883 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server number: 8.0.33.019-Jan-2017 01:37:15.883 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name: Windows Server 2008 R219-Jan-2017 01:37:15.883 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version: 6.119-Jan-2017 01:37:15.883 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture: amd6419-Jan-2017 01:37:15.883 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home: C:Program FilesJavajdk1.8.0_20jre19-Jan-2017 01:37:15.883 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version: 1.8.0_20-b2619-Jan-2017 01:37:15.884 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: Oracle Corporation19-Jan-2017 01:37:15.884 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: C:Program Filesapache-tomcat-8.0.33-windows-x64apache-tomcat-8.0.3319-Jan-2017 01:37:15.884 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: C:Program Filesapache-tomcat-8.0.33-windows-x64apache-tomcat-8.0.3319-Jan-2017 01:37:15.884 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=C:Program Filesapache-tomcat-8.0.33-windows-x64apache-tomcat-8.0.3319-Jan-2017 01:37:15.884 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=C:Program Filesapache-tomcat-8.0.33-windows-x64apache-tomcat-8.0.3319-Jan-2017 01:37:15.884 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.endorsed.dirs=C:Program Filesapache-tomcat-8.0.33-windows-x64apache-tomcat-8.0.33endorsed19-Jan-2017 01:37:15.884 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=C:Program Filesapache-tomcat-8.0.33-windows-x64apache-tomcat-8.0.33temp19-Jan-2017 01:37:15.885 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager19-Jan-2017 01:37:15.885 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=C:Program Filesapache-tomcat-8.0.33-windows-x64apache-tomcat-8.0.33conflogging.properties19-Jan-2017 01:37:15.885 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: exit19-Jan-2017 01:37:15.885 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xms128m19-Jan-2017 01:37:15.885 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xmx256m19-Jan-2017 01:37:15.885 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded APR based Apache Tomcat Native library 1.2.5 using APR version 1.5.1.19-Jan-2017 01:37:15.885 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].19-Jan-2017 01:37:16.522 INFO [main] org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL successfully initialized (OpenSSL 1.0.2g 1 Mar 2016)19-Jan-2017 01:37:16.659 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-apr-8081"]19-Jan-2017 01:37:16.669 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["ajp-apr-8010"]19-Jan-2017 01:37:16.670 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 1191 ms19-Jan-2017 01:37:16.698 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service Catalina19-Jan-2017 01:37:16.698 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.0.3319-Jan-2017 01:37:16.708 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory C:Program Filesapache-tomcat-8.0.33-windows-x64apache-tomcat-8.0.33webappsdocs19-Jan-2017 01:37:17.194 INFO [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanJars 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.19-Jan-2017 01:37:17.302 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory C:Program Filesapache-tomcat-8.0.33-windows-x64apache-tomcat-8.0.33webappsdocs has finished in 593 ms19-Jan-2017 01:37:17.302 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory C:Program Filesapache-tomcat-8.0.33-windows-x64apache-tomcat-8.0.33webappsexamples19-Jan-2017 01:37:17.742 INFO [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanJars 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.19-Jan-2017 01:37:17.790 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory C:Program Filesapache-tomcat-8.0.33-windows-x64apache-tomcat-8.0.33webappsexamples has finished in 488 ms19-Jan-2017 01:37:17.790 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory C:Program Filesapache-tomcat-8.0.33-windows-x64apache-tomcat-8.0.33webappshost-manager19-Jan-2017 01:37:17.994 INFO [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanJars 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.19-Jan-2017 01:37:17.998 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory C:Program Filesapache-tomcat-8.0.33-windows-x64apache-tomcat-8.0.33webappshost-manager has finished in 207 ms19-Jan-2017 01:37:17.998 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory C:Program Filesapache-tomcat-8.0.33-windows-x64apache-tomcat-8.0.33webappsjasperserver-pro19-Jan-2017 01:37:39.996 INFO [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanJars 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.19-Jan-2017 01:38:07.369 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file19-Jan-2017 01:38:07.370 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal Context [/jasperserver-pro] startup failed due to previous errors19-Jan-2017 01:38:07.428 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [jasperserver-pro] registered the JDBC driver [tibcosoftware.jdbc.oracle.OracleDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.19-Jan-2017 01:38:07.428 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [jasperserver-pro] registered the JDBC driver [tibcosoftware.jdbc.oracle.OracleDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.19-Jan-2017 01:38:07.428 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [jasperserver-pro] registered the JDBC driver [tibcosoftware.jdbc.sqlserver.SQLServerDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.19-Jan-2017 01:38:07.429 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [jasperserver-pro] registered the JDBC driver [tibcosoftware.jdbc.sqlserver.SQLServerDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.19-Jan-2017 01:38:07.429 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [jasperserver-pro] registered the JDBC driver [tibcosoftware.jdbc.db2.DB2Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.19-Jan-2017 01:38:07.429 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [jasperserver-pro] registered the JDBC driver [tibcosoftware.jdbc.db2.DB2Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.19-Jan-2017 01:38:07.429 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [jasperserver-pro] registered the JDBC driver [tibcosoftware.jdbc.hive.HiveDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.19-Jan-2017 01:38:07.429 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [jasperserver-pro] registered the JDBC driver [tibcosoftware.jdbc.hive.HiveDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.19-Jan-2017 01:38:07.429 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [jasperserver-pro] registered the JDBC driver [tibcosoftware.jdbc.impala.ImpalaDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.19-Jan-2017 01:38:07.429 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [jasperserver-pro] registered the JDBC driver [tibcosoftware.jdbc.impala.ImpalaDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.19-Jan-2017 01:38:07.429 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [jasperserver-pro] registered the JDBC driver [tibcosoftware.jdbc.mongodb.MongoDBDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.19-Jan-2017 01:38:07.429 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [jasperserver-pro] registered the JDBC driver [tibcosoftware.jdbc.mongodb.MongoDBDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.19-Jan-2017 01:38:07.430 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [jasperserver-pro] registered the JDBC driver [tibcosoftware.jdbc.redshift.RedshiftDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.19-Jan-2017 01:38:07.430 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [jasperserver-pro] registered the JDBC driver [tibcosoftware.jdbc.redshift.RedshiftDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.19-Jan-2017 01:38:07.430 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [jasperserver-pro] registered the JDBC driver [org.teiid.jdbc.TeiidDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.19-Jan-2017 01:38:07.431 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [jasperserver-pro] appears to have started a thread named [Thread-3] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.lang.Object.wait(Native Method) java.lang.Object.wait(Object.java:502) com.jaspersoft.jasperserver.war.themes.ThemeCache$RefreshThread.run(ThemeCache.java:316)19-Jan-2017 01:38:07.431 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [jasperserver-pro] appears to have started a thread named [CascadeCacheCleaner] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.lang.Object.wait(Native Method) java.util.TimerThread.mainLoop(Timer.java:552) java.util.TimerThread.run(Timer.java:505)19-Jan-2017 01:38:07.431 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [jasperserver-pro] appears to have started a thread named [quartzScheduler_Worker-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.lang.Object.wait(Native Method) org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:552)19-Jan-2017 01:38:07.432 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [jasperserver-pro] appears to have started a thread named [quartzScheduler_Worker-2] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.lang.Object.wait(Native Method) org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:552)19-Jan-2017 01:38:07.432 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [jasperserver-pro] appears to have started a thread named [bitronix-task-scheduler] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.lang.Thread.sleep(Native Method) bitronix.tm.timer.TaskScheduler.run(TaskScheduler.java:245)19-Jan-2017 01:38:07.433 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [jasperserver-pro] appears to have started a thread named [bufferManager Cleaner] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.lang.Object.wait(Native Method) org.teiid.common.buffer.impl.BufferManagerImpl$Cleaner.run(BufferManagerImpl.java:120) java.util.TimerThread.mainLoop(Timer.java:555) java.util.TimerThread.run(Timer.java:505)19-Jan-2017 01:38:07.433 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [jasperserver-pro] appears to have started a thread named [scheduled-eviction-thread-0] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: sun.misc.Unsafe.park(Native Method) java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215) java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078) java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1093) java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) java.lang.Thread.run(Thread.java:745)19-Jan-2017 01:38:07.434 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [jasperserver-pro] appears to have started a thread named [JasperServer Adhoc EhCache Cleaner] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.lang.Object.wait(Native Method) java.util.TimerThread.mainLoop(Timer.java:552) java.util.TimerThread.run(Timer.java:505)converted-file.txtLet me know the rootcause and how to resolve this issue Link to comment Share on other sites More sharing options...
hozawa Posted January 22, 2017 Share Posted January 22, 2017 The cause seems to be the following. Try moving webapps/jasperserver-pro to C: and try to start up Tomcat by itself. If this does not work, you didn't install tomcat correctly.19-Jan-2017 01:38:07.369 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now