Confluence crashes, login hangs & degrades

Hi, all;

This is my fourth Confluence installation, and it always happens the same. It works OK just after installation, but a few days later, it starts to degrade. Service crashes that need a reboot, login screens that hang up indefinitely, etc.

I've searched through the info available at your site, but haven't found anything that solves this issue. My only option is to reinstall.

We were considering upgrading to a higher license but not if this application isn't reliable. We already use JIRA without issues.

Thank you very much in advance, best regards;

1 answer

0 vote

What does the log say?  Have you given it enough resources?

Thanks for answering.

As for resources, it's a VM with 4 cores, 8192 MB RAM, and 60 GB hard disk. Should be enough as it's only me who's testing it.

As for logs, a few errors indeed. I'm copying a few lines, but I could zip any file you may eventually need. Right now it's mostly this:

2017-08-21 11:29:01,980 WARN [synchrony-interop-executor:thread-2] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] pollHealthcheck Could not ping the synchrony-proxy [http://127.0.0.1:8090/synchrony-proxy/healthcheck]: {}
org.apache.http.conn.HttpHostConnectException: Connect to 127.0.0.1:8090 [/127.0.0.1] failed: Connection refused: connect
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:151)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380)
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
at com.atlassian.confluence.plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor.pollHealthcheck(DefaultSynchronyProxyMonitor.java:76)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:74)
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:134)
... 15 more

That suggests that Synchrony is not running, or can't be connected to.  Is there a separate process running for it?

Yeah. Thing is, this is a completely default installation, so Synchrony should be untouched. Could you help me locating and troubleshooting it?

So it is running?

I don't know. There's nothing related to "synchrony" on the "Services" pane of Computer Management. If it is a part of Confluence, how can I check it?

It's a process that runs alongside Confluence in the same way - as a server.  It should appear in the task list in the same place.

Well, if that's the case, it doesn't show. Neither as a service nor as a process. How can I start it?

It should start as Confluence starts, but you can try to restart it by going to admin -> collaborative editing, and toggling it off and on again.

After you've done that, take a look at the logs, as I'd expect it to have failed, but you should then see startup failures.  Look under the Confluence installation/log directory.

Sorry, I'm unable to do this, Confluence's web page doesn't load, even after a reboot. Is there any other way to disable Synchrony, as I wouldn't be needing collaborative editing for the time being?

If you can't get into Confluence to get to that screen, the problem is not Synchrony.

You'll need to look through your logs to find out why it's so slow.  Look at the installation and look at what you configured differently to the defaults.  Are you on a supported system?

Ok, so this has been a almost-by-the-book default install. Database is PostgreSQL, database and user names are the same as per Atlassian web howto.

About support, our Confluence is on a starter license. We have been using JIRA 25 users for several years now, still supported. I'm testing Confluence as we would consider buying it as well.

I've disabled the synchrony.proxy.healthcheck variable, and now the log looks quite clean, although the website still doesn't load anymore.

As I've said before... This was working OK since installation, for several days, even after several reboots. Up until one day it decides to stop working, which is really frustrating.

Here's atlassian-confluence.log for my last reboot:

2017-08-22 12:36:36,713 INFO [localhost-startStop-1] [com.atlassian.confluence.lifecycle] contextInitialized Starting Confluence 6.3.2 [build 7202 based on commit hash 2b917bf474320363b63231a29396d24a46356543] - synchrony version 1.0.0-release-confluence_6.1-78073294
2017-08-22 12:36:41,151 INFO [localhost-startStop-1] [atlassian.confluence.cluster.DefaultClusterConfigurationHelper] lambda$populateExistingClusterSetupConfig$1 Populating setup configuration if running with Cluster mode...
2017-08-22 12:36:41,276 INFO [localhost-startStop-1] [springframework.web.context.ContextLoader] initWebApplicationContext Root WebApplicationContext: initialization started
2017-08-22 12:36:46,182 INFO [localhost-startStop-1] [com.atlassian.confluence.lifecycle] <init> Loading EhCache cache manager
2017-08-22 12:37:03,979 INFO [localhost-startStop-1] [springframework.web.context.ContextLoader] initWebApplicationContext Root WebApplicationContext: initialization completed in 22703 ms
2017-08-22 12:37:05,198 INFO [localhost-startStop-1] [atlassian.plugin.manager.DefaultPluginManager] earlyStartup Plugin system earlyStartup begun
2017-08-22 12:37:37,376 WARN [ThreadPoolAsyncTaskExecutor::Thread 5] [spring.scanner.util.ProductFilterUtil] detectProduct Couldn't detect product, will use ProductFilter.ALL
2017-08-22 12:37:37,408 WARN [ThreadPoolAsyncTaskExecutor::Thread 2] [spring.scanner.util.ProductFilterUtil] detectProduct Couldn't detect product, will use ProductFilter.ALL
2017-08-22 12:37:39,455 WARN [ThreadPoolAsyncTaskExecutor::Thread 4] [spring.scanner.util.ProductFilterUtil] detectProduct Couldn't detect product, will use ProductFilter.ALL
2017-08-22 12:37:56,392 INFO [localhost-startStop-1] [atlassian.plugin.manager.DefaultPluginManager] logTime Plugin system earlyStartup ended
2017-08-22 12:37:56,626 INFO [localhost-startStop-1] [atlassian.plugin.manager.DefaultPluginManager] lateStartup Plugin system lateStartup begun
2017-08-22 12:37:57,876 WARN [AtlassianEvent::CustomizableThreadFactory-1] [persistence.schema.hibernate.HibernateSchemaComparator] lambda$compareTables$0 Schema check for table [EVENTS] encountered an error. Turn debug logging on for stacktrace.
2017-08-22 12:37:57,892 WARN [AtlassianEvent::CustomizableThreadFactory-1] [persistence.schema.hibernate.HibernateSchemaComparator] lambda$compareTables$0 Schema check for table [SECRETS] encountered an error. Turn debug logging on for stacktrace.
2017-08-22 12:37:57,892 WARN [AtlassianEvent::CustomizableThreadFactory-1] [persistence.schema.hibernate.HibernateSchemaComparator] lambda$compareTables$0 Schema check for table [SNAPSHOTS] encountered an error. Turn debug logging on for stacktrace.
2017-08-22 12:37:59,048 WARN [ThreadPoolAsyncTaskExecutor::Thread 2] [client.eventfilter.whitelist.AnalyticsWhitelistModuleDescriptor] readPluginWhitelist No whitelist resource file found at [mediaviewer/lib/analytics-whitelist.json] in plugin [com.atlassian.confluence.plugins.confluence-previews] (bundle entry not found)
2017-08-22 12:37:59,189 WARN [ThreadPoolAsyncTaskExecutor::Thread 2] [client.eventfilter.whitelist.AnalyticsWhitelistModuleDescriptor] readPluginWhitelist No whitelist resource file found at [mediaviewer/lib/analytics-whitelist.json] in plugin [com.atlassian.confluence.plugins.confluence-previews] (null InputStream)
2017-08-22 12:38:02,892 INFO [ThreadPoolAsyncTaskExecutor::Thread 1] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] <init> synchrony-proxy healthcheck url: http://127.0.0.1:8090/synchrony-proxy/healthcheck
2017-08-22 12:38:03,361 ERROR [ThreadPoolAsyncTaskExecutor::Thread 10] [spring.scanner.extension.ComponentImportBeanFactoryPostProcessor] postProcessBeanFactory Unable to load class 'com.atlassian.bitbucket.auth.RememberMeService' for component importation purposes. Skipping...
2017-08-22 12:38:03,361 ERROR [ThreadPoolAsyncTaskExecutor::Thread 10] [spring.scanner.extension.ComponentImportBeanFactoryPostProcessor] postProcessBeanFactory Unable to load class 'com.atlassian.jira.config.properties.ApplicationProperties' for component importation purposes. Skipping...
2017-08-22 12:38:05,064 INFO [localhost-startStop-1] [atlassian.plugin.manager.DefaultPluginManager] logTime Plugin system lateStartup ended
2017-08-22 12:38:05,189 WARN [lifecycle:thread-30] [expose.jmx.schedule.JmxInstrumentSchedulerImpl] onStart atlassian-instrumentation-jmx expose scheduler started.
2017-08-22 12:38:05,189 INFO [lifecycle:thread-31] [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] startup Starting Synchrony and enabling Collaborative Editing
2017-08-22 12:38:05,267 INFO [synchrony-interop-executor:thread-1] [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] isSynchronyProxyEnabled proxy port present: false
2017-08-22 12:38:05,267 INFO [synchrony-interop-executor:thread-1] [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] isSynchronyProxyEnabled app config synchrony.proxy.enabled: true
2017-08-22 12:38:05,392 WARN [lifecycle:thread-23] [hql.internal.ast.HqlSqlWalker] generatePositionalParameter [DEPRECATION] Encountered positional parameter near line 1, column 93 in HQL: [FROM com.atlassian.confluence.impl.schedule.caesium.SchedulerClusteredJob t WHERE t.jobId = ?]. Positional parameter are considered deprecated; use named parameters or JPA-style positional parameters instead.
2017-08-22 12:38:06,720 WARN [UpmScheduler:thread-1] [hql.internal.ast.HqlSqlWalker] generatePositionalParameter [DEPRECATION] Encountered positional parameter near line 1, column 110 in HQL: [SELECT usr.name, usr.lowerName FROM com.atlassian.crowd.model.user.InternalUser usr WHERE usr.directory.id = ? AND usr.active = ? ORDER BY usr.lowerName]. Positional parameter are considered deprecated; use named parameters or JPA-style positional parameters instead.
2017-08-22 12:38:06,720 WARN [UpmScheduler:thread-1] [hql.internal.ast.HqlSqlWalker] generatePositionalParameter [DEPRECATION] Encountered positional parameter near line 1, column 129 in HQL: [SELECT usr.name, usr.lowerName FROM com.atlassian.crowd.model.user.InternalUser usr WHERE usr.directory.id = ? AND usr.active = ? ORDER BY usr.lowerName]. Positional parameter are considered deprecated; use named parameters or JPA-style positional parameters instead.
2017-08-22 12:38:07,122 WARN [UpmScheduler:thread-1] [hql.internal.ast.HqlSqlWalker] generatePositionalParameter [DEPRECATION] Encountered positional parameter near line 1, column 159 in HQL: [SELECT mem.userMember.name FROM com.atlassian.crowd.embedded.hibernate2.HibernateMembership mem WHERE mem.groupMember is null and mem.parentGroup.lowerName = ? and mem.parentGroup.directory.id = ? and mem.parentGroup.type = ? ORDER BY mem.userMember.lowerName]. Positional parameter are considered deprecated; use named parameters or JPA-style positional parameters instead.
2017-08-22 12:38:07,122 WARN [UpmScheduler:thread-1] [hql.internal.ast.HqlSqlWalker] generatePositionalParameter [DEPRECATION] Encountered positional parameter near line 1, column 196 in HQL: [SELECT mem.userMember.name FROM com.atlassian.crowd.embedded.hibernate2.HibernateMembership mem WHERE mem.groupMember is null and mem.parentGroup.lowerName = ? and mem.parentGroup.directory.id = ? and mem.parentGroup.type = ? ORDER BY mem.userMember.lowerName]. Positional parameter are considered deprecated; use named parameters or JPA-style positional parameters instead.
2017-08-22 12:38:07,122 WARN [UpmScheduler:thread-1] [hql.internal.ast.HqlSqlWalker] generatePositionalParameter [DEPRECATION] Encountered positional parameter near line 1, column 225 in HQL: [SELECT mem.userMember.name FROM com.atlassian.crowd.embedded.hibernate2.HibernateMembership mem WHERE mem.groupMember is null and mem.parentGroup.lowerName = ? and mem.parentGroup.directory.id = ? and mem.parentGroup.type = ? ORDER BY mem.userMember.lowerName]. Positional parameter are considered deprecated; use named parameters or JPA-style positional parameters instead.
2017-08-22 12:38:07,455 INFO [UpmScheduler:thread-1] [atlassian.confluence.user.DefaultUserAccessor] getUserNamesWithConfluenceAccess Found USE permission with no associated username or group: [USECONFLUENCE,0,null,null,null]
2017-08-22 12:38:11,491 INFO [synchrony-interop-executor:thread-1] [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] debugPrintEnvironment Synchrony working dir: C:\Program Files\Atlassian\Application Data\Confluence
2017-08-22 12:38:11,491 INFO [synchrony-interop-executor:thread-1] [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] debugPrintEnvironment C:\Program Files\Atlassian\Confluence\jre\bin\java.exe -classpath C:\Program Files\Atlassian\Confluence\temp\1.0.0-release-confluence_6.1-78073294.jar;C:\Program Files\Atlassian\Confluence\confluence\WEB-INF\lib\postgresql-42.1.1.jar -Xss2048k -Xmx1g synchrony.core sql
2017-08-22 12:38:12,227 INFO [ListenableFutureAdapter-thread-1] [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] isSynchronyProxyEnabled proxy port present: false
2017-08-22 12:38:12,227 INFO [ListenableFutureAdapter-thread-1] [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] isSynchronyProxyEnabled app config synchrony.proxy.enabled: true
2017-08-22 12:38:12,242 INFO [ListenableFutureAdapter-thread-1] [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] updateSynchronyConfiguration Synchrony External Base URL: http://10.234.2.118:8090/synchrony-proxy,http://10.234.2.118:8090/synchrony-proxy
2017-08-22 12:38:12,242 INFO [ListenableFutureAdapter-thread-1] [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] updateSynchronyConfiguration Synchrony External Service URL: http://10.234.2.118:8090/synchrony-proxy/v1
2017-08-22 12:38:12,242 INFO [ListenableFutureAdapter-thread-1] [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] updateSynchronyConfiguration Synchrony Internal Service URL: http://127.0.0.1:8091/synchrony/v1
2017-08-22 12:38:24,665 WARN [ListenableFutureAdapter-thread-2] [plugins.synchrony.config.DefaultSynchronyConfigurationManager] enableSharedDrafts [Collab editing plugin] Enabling Shared Drafts

Ok, what does "the website does not load" mean?  Errors?  Not found?

Blank page, titled "Waiting for localhost", icon spinning.

Ok, that makes me want to look at Catalina.out first, and then check the confluence log again for the area where you first tried to access it.

A spinner often means that the Tomcat has started, but Confluence has not come up.  Catalina.out may tell us why if it's simply failing, but if it is partially starting, then the errors may also be being dumped into the confluence log.

Ok, here we go. First, catalina.out for this last run:

 

22-Aug-2017 12:36:25.026 WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin [SetPropertiesRule]{Server} Setting property 'debug' to '0' did not find a matching property.
22-Aug-2017 12:36:25.307 WARNING [main] org.apache.catalina.startup.SetAllPropertiesRule.begin [SetAllPropertiesRule]{Server/Service/Connector} Setting property 'debug' to '0' did not find a matching property.
22-Aug-2017 12:36:25.338 WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin [SetPropertiesRule]{Server/Service/Engine} Setting property 'debug' to '0' did not find a matching property.
22-Aug-2017 12:36:25.338 WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin [SetPropertiesRule]{Server/Service/Engine/Host} Setting property 'debug' to '0' did not find a matching property.
22-Aug-2017 12:36:25.401 WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'debug' to '0' did not find a matching property.
22-Aug-2017 12:36:25.447 WARNING [main] org.apache.catalina.core.StandardContext.setPath A context path must either be an empty string or start with a '/' and do not end with a '/'. The path [${confluence.context.path}/synchrony-proxy] does not meet these criteria and has been changed to [/${confluence.context.path}/synchrony-proxy]
22-Aug-2017 12:36:25.447 WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'debug' to '0' did not find a matching property.
22-Aug-2017 12:36:26.322 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8090"]
22-Aug-2017 12:36:27.287 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
22-Aug-2017 12:36:27.287 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 2692 ms
22-Aug-2017 12:36:27.318 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service Tomcat-Standalone
22-Aug-2017 12:36:27.318 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.0.43
22-Aug-2017 12:36:33.085 INFO [localhost-startStop-2] 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.
22-Aug-2017 12:36:33.898 INFO [localhost-startStop-2] org.apache.catalina.core.ApplicationContext.log Spring WebApplicationInitializers detected on classpath: [com.atlassian.synchrony.proxy.SynchronyDispatcherServletInitializer@3ad60935]
22-Aug-2017 12:36:34.304 INFO [localhost-startStop-2] org.apache.catalina.core.ApplicationContext.log Initializing Spring FrameworkServlet 'dispatcher'
22-Aug-2017 12:36:34.304 INFO [localhost-startStop-2] org.springframework.web.servlet.DispatcherServlet.initServletBean FrameworkServlet 'dispatcher': initialization started
22-Aug-2017 12:36:34.304 INFO [localhost-startStop-2] org.springframework.web.context.support.AnnotationConfigWebApplicationContext.prepareRefresh Refreshing WebApplicationContext for namespace 'dispatcher-servlet': startup date [Tue Aug 22 12:36:34 CEST 2017]; root of context hierarchy
22-Aug-2017 12:36:34.398 INFO [localhost-startStop-2] org.springframework.web.context.support.AnnotationConfigWebApplicationContext.loadBeanDefinitions Registering annotated classes: [class com.atlassian.synchrony.proxy.websocket.WebSocketConfig,class com.atlassian.synchrony.proxy.web.SynchronyWebMvcConfig]
22-Aug-2017 12:36:35.038 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.
22-Aug-2017 12:36:35.101 INFO [localhost-startStop-2] org.springframework.scheduling.concurrent.ThreadPoolTaskScheduler.initialize Initializing ExecutorService 'defaultSockJsTaskScheduler'
22-Aug-2017 12:36:35.948 INFO [localhost-startStop-2] org.springframework.web.socket.server.support.WebSocketHandlerMapping.registerHandler Mapped URL path [/sockjs/v1/**] onto handler of type [class org.springframework.web.socket.sockjs.support.SockJsHttpRequestHandler]
22-Aug-2017 12:36:36.416 INFO [localhost-startStop-2] org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.initControllerAdviceCache Looking for @ControllerAdvice: WebApplicationContext for namespace 'dispatcher-servlet': startup date [Tue Aug 22 12:36:34 CEST 2017]; root of context hierarchy
22-Aug-2017 12:36:36.463 INFO [localhost-startStop-2] org.springframework.web.servlet.handler.SimpleUrlHandlerMapping.registerHandler Mapped URL path [/**] onto handler of type [class org.springframework.web.servlet.resource.DefaultServletHttpRequestHandler]
22-Aug-2017 12:36:36.526 INFO [localhost-startStop-2] org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerMapping.register Mapped "{[/reload],methods=[PUT]}" onto public org.springframework.http.ResponseEntity com.atlassian.synchrony.proxy.web.SynchronyProxyRestController.reloadConfiguration(com.atlassian.synchrony.proxy.web.SynchronyProxyConfigPayload)
22-Aug-2017 12:36:36.526 INFO [localhost-startStop-2] org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerMapping.register Mapped "{[/healthcheck]}" onto public com.atlassian.synchrony.proxy.web.HealthCheckResult com.atlassian.synchrony.proxy.web.SynchronyProxyRestController.getSynchronyProxyInfo()
22-Aug-2017 12:36:36.619 INFO [localhost-startStop-2] org.springframework.context.support.DefaultLifecycleProcessor.start Starting beans in phase 2147483647
22-Aug-2017 12:36:36.651 INFO [localhost-startStop-2] org.springframework.web.servlet.DispatcherServlet.initServletBean FrameworkServlet 'dispatcher': initialization completed in 2347 ms

If you need it, confluence stderr:


2017-08-22 12:36:20 Commons Daemon procrun stderr initialized
22-Aug-2017 12:36:25.026 WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin [SetPropertiesRule]{Server} Setting property 'debug' to '0' did not find a matching property.
22-Aug-2017 12:36:25.307 WARNING [main] org.apache.catalina.startup.SetAllPropertiesRule.begin [SetAllPropertiesRule]{Server/Service/Connector} Setting property 'debug' to '0' did not find a matching property.
22-Aug-2017 12:36:25.338 WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin [SetPropertiesRule]{Server/Service/Engine} Setting property 'debug' to '0' did not find a matching property.
22-Aug-2017 12:36:25.338 WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin [SetPropertiesRule]{Server/Service/Engine/Host} Setting property 'debug' to '0' did not find a matching property.
22-Aug-2017 12:36:25.401 WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'debug' to '0' did not find a matching property.
22-Aug-2017 12:36:25.447 WARNING [main] org.apache.catalina.core.StandardContext.setPath A context path must either be an empty string or start with a '/' and do not end with a '/'. The path [${confluence.context.path}/synchrony-proxy] does not meet these criteria and has been changed to [/${confluence.context.path}/synchrony-proxy]
22-Aug-2017 12:36:25.447 WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'debug' to '0' did not find a matching property.
22-Aug-2017 12:36:26.322 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8090"]
22-Aug-2017 12:36:27.287 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
22-Aug-2017 12:36:27.287 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 2692 ms
22-Aug-2017 12:36:27.318 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service Tomcat-Standalone
22-Aug-2017 12:36:27.318 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.0.43
22-Aug-2017 12:36:33.085 INFO [localhost-startStop-2] 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.
22-Aug-2017 12:36:33.898 INFO [localhost-startStop-2] org.apache.catalina.core.ApplicationContext.log Spring WebApplicationInitializers detected on classpath: [com.atlassian.synchrony.proxy.SynchronyDispatcherServletInitializer@3ad60935]
22-Aug-2017 12:36:34.304 INFO [localhost-startStop-2] org.apache.catalina.core.ApplicationContext.log Initializing Spring FrameworkServlet 'dispatcher'
22-Aug-2017 12:36:34.304 INFO [localhost-startStop-2] org.springframework.web.servlet.DispatcherServlet.initServletBean FrameworkServlet 'dispatcher': initialization started
22-Aug-2017 12:36:34.304 INFO [localhost-startStop-2] org.springframework.web.context.support.AnnotationConfigWebApplicationContext.prepareRefresh Refreshing WebApplicationContext for namespace 'dispatcher-servlet': startup date [Tue Aug 22 12:36:34 CEST 2017]; root of context hierarchy
22-Aug-2017 12:36:34.398 INFO [localhost-startStop-2] org.springframework.web.context.support.AnnotationConfigWebApplicationContext.loadBeanDefinitions Registering annotated classes: [class com.atlassian.synchrony.proxy.websocket.WebSocketConfig,class com.atlassian.synchrony.proxy.web.SynchronyWebMvcConfig]
22-Aug-2017 12:36:35.038 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.
22-Aug-2017 12:36:35.101 INFO [localhost-startStop-2] org.springframework.scheduling.concurrent.ThreadPoolTaskScheduler.initialize Initializing ExecutorService 'defaultSockJsTaskScheduler'
22-Aug-2017 12:36:35.948 INFO [localhost-startStop-2] org.springframework.web.socket.server.support.WebSocketHandlerMapping.registerHandler Mapped URL path [/sockjs/v1/**] onto handler of type [class org.springframework.web.socket.sockjs.support.SockJsHttpRequestHandler]
22-Aug-2017 12:36:36.416 INFO [localhost-startStop-2] org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.initControllerAdviceCache Looking for @ControllerAdvice: WebApplicationContext for namespace 'dispatcher-servlet': startup date [Tue Aug 22 12:36:34 CEST 2017]; root of context hierarchy
22-Aug-2017 12:36:36.463 INFO [localhost-startStop-2] org.springframework.web.servlet.handler.SimpleUrlHandlerMapping.registerHandler Mapped URL path [/**] onto handler of type [class org.springframework.web.servlet.resource.DefaultServletHttpRequestHandler]
22-Aug-2017 12:36:36.526 INFO [localhost-startStop-2] org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerMapping.register Mapped "{[/reload],methods=[PUT]}" onto public org.springframework.http.ResponseEntity com.atlassian.synchrony.proxy.web.SynchronyProxyRestController.reloadConfiguration(com.atlassian.synchrony.proxy.web.SynchronyProxyConfigPayload)
22-Aug-2017 12:36:36.526 INFO [localhost-startStop-2] org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerMapping.register Mapped "{[/healthcheck]}" onto public com.atlassian.synchrony.proxy.web.HealthCheckResult com.atlassian.synchrony.proxy.web.SynchronyProxyRestController.getSynchronyProxyInfo()
22-Aug-2017 12:36:36.619 INFO [localhost-startStop-2] org.springframework.context.support.DefaultLifecycleProcessor.start Starting beans in phase 2147483647
22-Aug-2017 12:36:36.651 INFO [localhost-startStop-2] org.springframework.web.servlet.DispatcherServlet.initServletBean FrameworkServlet 'dispatcher': initialization completed in 2347 ms

So it's starting ok.  What does the application log say from the point of start up?  What is the server doing as well?  Thrashing cpu/memory/disk etc?

Hi, Nic;

Just got surprised today, as it's started working again... right after I enabled all connections to the Internet from the host (at my edge firewall).

Why has this happened, no idea. I started having issues with my JIRA installation as well, so things got more serious. Somewhere in JIRA logs was a failed connection to some amazon aws domain, so I openened the firewall policy and surprise, JIRA loaded. Did the same with Confluence, and it all went well.

I've sent some logs to the support team regarding JIRA, so that they can check why this behaviour happens on both apps.

Thanks for all your help and time.

Best regards!

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Kesha Thillainayagam
Posted Apr 13, 2018 in Confluence

We want to hear how your non-technical teams are using Confluence!

Hi Community! Kesha (kay-sha) from the Confluence marketing team here! Can you share stories with us on how your non-technical (think Marketing, Sales, HR, legal, etc.) teams are using Confluen...

1,915 views 25 10
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you