confluence 6 minutes to start
Asked by anael savioz:

Hi,  

I have noticed that my confluence process need 6 minutes and 6-9 seconds to be available.  
And each time the same load time.

I have doubled the CPU / RAM on the VM =\> same time

I have put the VM on a SSN datastore =\> same time

It seems to be some kind of a time out, but I am unable to identify the source.  
Do you have any hint or RTFM ?

My setup is : CentOS 7 / Confluence 5.10.4 / No NFS.  

```
ed selector for servlet write/read22-Sep-2016 12:56:35.209 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 326 ms22-Sep-2016 12:56:35.213 INFO [main] org.apache.catalina.core.StandardService.startInternal D??marrage du service Tomcat-Standalone22-Sep-2016 12:56:35.213 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.0.362016-09-22 12:56:43,275 INFO [localhost-startStop-1] [com.atlassian.confluence.lifecycle] contextInitialized Starting Confluence 5.10.4 [build 6441 based on commit hash 7d28db648b08c18ff79fe305b2da56665a84a1fc]?&lt;&lt; 6 minutes WAIT HERE &gt;&gt;?22-Sep-2016 13:02:51.046 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8090"]22-Sep-2016 13:02:51.055 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 375845 ms22-Sep-2016 13:02:51.572 INFO [http-nio-8090-exec-8] com.sun.jersey.server.impl.application.WebApplicationImpl._initiate Initiating Jersey application, version 'Jersey: 1.8-atlassian-16 03/23/2015 10:20 PM'22-Sep-2016 13:02:51.735 INFO [http-nio-8090-exec-2] com.sun.jersey.server.impl.application.WebApplicationImpl._initiate Initiating Jersey application, version 'Jersey: 1.8-atlassian-16 03/23/2015 10:20 PM'22-Sep-2016 13:02:51.776 INFO [http-nio-8090-exec-1] com.sun.jersey.server.impl.application.WebApplicationImpl._initiate Initiating Jersey application, version 'Jersey: 1.8-atlassian-16 03/23/2015 10:20 PM'
```


Answers:
author: Khuong Vu
body: FYI, my application took 18 minutes to come up. (I waited 18 minutes, because I did not see any errors that I could act on.) It turned out that the 18-minutes wait was caused by my recent upgrades: (a) upgrading from MySQL 5.5 to 5.6, (b) upgrading Confluence from 5.7 to 6.0, which requires MySQL 5.6.19 or higher but not 5.7.

My old settings in MySQL 5.5 was giving me problems. After changing the settings, the application started up in 2.5 minutes.

The old settings were:

innodb_log_files_in_group=100

innodb_log_file_size=5M

The new settings were:

innodb_log_files_in_group=12

innodb_log_file_size=256M


author: anael savioz
body: VMware - Last CPU generation. I have doubled the CPU count and no change.  
SElinux ON/OFF no change  
Antivirus ON/OFF no change.  

I haven't tried the Safe mode =\> also no changes.  

<br />

The [Atlassian Marketplace](https://marketplace.atlassian.com/) server is not reachable. It could be my problem.

comments: author: Pavel Potcheptsov
body: So your server doesn't have Internet connection?


author: Nadeem Zakir
body: Any update on this? we are also seeing a 6 minutes wait. same log messages as Original poster. On Confluence 6.01 and SQL 2012


author: Pavel Potcheptsov
body: What is your virtual environment, especially what is you CPU type? Have you tried to change CPU type to Nehalem or Host?

Have you tried to put your instance to Safe mode by disabling all plugins and restart to see for changes in starting delay.

Have you tried to disable SElinux?

Do you have some anti viruses?


Tags: confluence-administration