Start_Service.bat not fully started?

[Alex Holcomb]

after running start_service.bat I go to the launch in browser link, and end up with a 404 error.

Below is the Catalina log file from this attempt at running Start_service.bat

Any steps forward would be appreciated.

Oct 03, 2014 9:47:23 AM org.apache.coyote.AbstractProtocol pause INFO: Pausing ProtocolHandler ["http-bio-8090"]

Oct 03, 2014 9:47:23 AM org.apache.catalina.core.StandardService stopInternal INFO: Stopping service Tomcat-Standalone

Oct 03, 2014 9:47:23 AM org.apache.coyote.AbstractProtocol stop INFO: Stopping ProtocolHandler ["http-bio-8090"]

Oct 03, 2014 9:50:46 AM org.apache.tomcat.util.digester.SetPropertiesRule begin WARNING: [SetPropertiesRule]{Server} Setting property 'debug' to '0' did not find a matching property.

Oct 03, 2014 9:50:46 AM org.apache.catalina.startup.SetAllPropertiesRule begin WARNING: [SetAllPropertiesRule]{Server/Service/Connector} Setting property 'minProcessors' to '5' did not find a matching property.

Oct 03, 2014 9:50:46 AM org.apache.catalina.startup.SetAllPropertiesRule begin WARNING: [SetAllPropertiesRule]{Server/Service/Connector} Setting property 'maxProcessors' to '75' did not find a matching property.

 Oct 03, 2014 9:50:46 AM org.apache.catalina.startup.SetAllPropertiesRule begin WARNING: [SetAllPropertiesRule]{Server/Service/Connector} Setting property 'debug' to '0' did not find a matching property.

Oct 03, 2014 9:50:46 AM org.apache.catalina.startup.SetAllPropertiesRule begin WARNING: [SetAllPropertiesRule]{Server/Service/Connector} Setting property 'useURIValidationHack' to 'false' did not find a matching property.

Oct 03, 2014 9:50:46 AM org.apache.tomcat.util.digester.SetPropertiesRule begin WARNING: [SetPropertiesRule]{Server/Service/Engine} Setting property 'debug' to '0' did not find a matching property.

Oct 03, 2014 9:50:46 AM org.apache.tomcat.util.digester.SetPropertiesRule begin WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting property 'debug' to '0' did not find a matching property.

Oct 03, 2014 9:50:46 AM org.apache.tomcat.util.digester.SetPropertiesRule begin WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'debug' to '0' did not find a matching property.

Oct 03, 2014 9:50:47 AM org.apache.coyote.AbstractProtocol init INFO: Initializing ProtocolHandler ["http-bio-8090"]

Oct 03, 2014 9:50:47 AM org.apache.catalina.startup.Catalina load INFO: Initialization processed in 1389 ms

Oct 03, 2014 9:50:47 AM org.apache.catalina.core.StandardService startInternal INFO: Starting service Tomcat-Standalone

Oct 03, 2014 9:50:47 AM org.apache.catalina.core.StandardEngine startInternal INFO: Starting Servlet Engine: Apache Tomcat/7.0.52

Oct 03, 2014 9:57:48 AM org.apache.catalina.core.StandardContext startInternal SEVERE: Error listenerStart

Oct 03, 2014 9:57:48 AM org.apache.catalina.core.StandardContext startInternal SEVERE: Context [] startup failed due to previous errors

Oct 03, 2014 9:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc SEVERE: The web application [] registered the JDBC driver [org.hsqldb.jdbc.JDBCDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

Oct 03, 2014 9:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc SEVERE: The web application [] registered the JDBC driver [org.postgresql.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

Oct 03, 2014 9:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc SEVERE: The web application [] registered the JDBC driver [net.sourceforge.jtds.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

Oct 03, 2014 9:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [Statistics Thread-__DEFAULT__-1] but has failed to stop it. This is very likely to create a memory leak.

Oct 03, 2014 9:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [scheduler_Worker-1] but has failed to stop it. This is very likely to create a memory leak.

Oct 03, 2014 9:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [scheduler_Worker-2] but has failed to stop it. This is very likely to create a memory leak.

Oct 03, 2014 9:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [scheduler_Worker-3] but has failed to stop it. This is very likely to create a memory leak.

Oct 03, 2014 9:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [scheduler_Worker-4] but has failed to stop it. This is very likely to create a memory leak.

Oct 03, 2014 9:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [scheduler_Worker-5] but has failed to stop it. This is very likely to create a memory leak.

Oct 03, 2014 9:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [scheduler_Worker-6] but has failed to stop it. This is very likely to create a memory leak.

Oct 03, 2014 9:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [scheduler_Worker-7] but has failed to stop it. This is very likely to create a memory leak.

Oct 03, 2014 9:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [scheduler_Worker-8] but has failed to stop it. This is very likely to create a memory leak.

Oct 03, 2014 9:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [scheduler_Worker-9] but has failed to stop it. This is very likely to create a memory leak.

Oct 03, 2014 9:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [scheduler_Worker-10] but has failed to stop it. This is very likely to create a memory leak.

Oct 03, 2014 9:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [Timer-0] but has failed to stop it. This is very likely to create a memory leak.

Oct 03, 2014 9:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0] but has failed to stop it. This is very likely to create a memory leak.

Oct 03, 2014 9:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1] but has failed to stop it. This is very likely to create a memory leak.

Oct 03, 2014 9:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2] but has failed to stop it. This is very likely to create a memory leak.

Oct 03, 2014 9:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [Timer-1] but has failed to stop it. This is very likely to create a memory leak.

Oct 03, 2014 9:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0] but has failed to stop it. This is very likely to create a memory leak.

Oct 03, 2014 9:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1] but has failed to stop it. This is very likely to create a memory leak.

Oct 03, 2014 9:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2] but has failed to stop it. This is very likely to create a memory leak.

Oct 03, 2014 9:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [Timer-2] but has failed to stop it. This is very likely to create a memory leak.

Oct 03, 2014 9:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0] but has failed to stop it. This is very likely to create a memory leak.

Oct 03, 2014 9:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1] but has failed to stop it. This is very likely to create a memory leak.

 Oct 03, 2014 9:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2] but has failed to stop it. This is very likely to create a memory leak.

Oct 03, 2014 9:57:49 AM org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler ["http-bio-8090"]

Oct 03, 2014 9:57:49 AM org.apache.catalina.startup.Catalina start INFO: Server startup in 421516 ms

[Alex Holcomb]

Part of the services were held/running on a separate server. Those needed to be turned on before both servers would work. 

[Bill Hutton]

Was there ever an answer to this problem

[Tiago Comasseto]

Hi Alex, this log doesn't clearly indicate the problem, you may want to check the atlassian-confluence.log, but judging by some lines referring to JDBC I assume it could be a problem to connect to the database.

I hope it helps.

Cheers

[Alex Holcomb]

The log below is from the last two times I ran the start_service.bat Are they more telling? 2014-10-03 09:19:06 Commons Daemon procrun stdout initialized 2014-10-03 09:19:49,261 INFO [localhost-startStop-1] [com.atlassian.confluence.lifecycle] contextInitialized Starting Confluence 5.6.1 [build 5635 based on commit hash 60fd2eb45debbf4ede2b669f4c9b96b4ce40a937] 2014-10-03 09:19:54,432 WARN [localhost-startStop-1] [atlassian.config.xml.AbstractDom4jXmlConfigurationPersister] saveDocumentAtomically Unable to move C:\Program Files\Atlassian\Application Data\Confluence-2014\confluence.cfg.xml4246365303384460182tmp to C:\Program Files\Atlassian\Application Data\Confluence-2014\confluence.cfg.xml. Falling back to non-atomic overwrite. 2014-10-03 09:50:46 Commons Daemon procrun stdout initialized 2014-10-03 09:51:05,470 INFO [localhost-startStop-1] [com.atlassian.confluence.lifecycle] contextInitialized Starting Confluence 5.6.1 [build 5635 based on commit hash 60fd2eb45debbf4ede2b669f4c9b96b4ce40a937] 2014-10-03 09:51:09,434 WARN [localhost-startStop-1] [atlassian.config.xml.AbstractDom4jXmlConfigurationPersister] saveDocumentAtomically Unable to move C:\Program Files\Atlassian\Application Data\Confluence-2014\confluence.cfg.xml4026504260072770761tmp to C:\Program Files\Atlassian\Application Data\Confluence-2014\confluence.cfg.xml. Falling back to non-atomic overwrite.