Confluence Uses >=40% CPU (possible caching issue?)

I installed Confluence 4.2.7 w/ MySQL support on a virtual machine (vmware) with SuSE Linux. MySQL DB and Confluence are on the same VM installation.

Startup of Confluence is awfully slow (>400.000msec the logs state), but the system continously uses 40% CPU at least. After startup, using confluence is possible (no NPE or other exceptions) but it's slow (not unusable slow, but slow).

Various memory settings (-Xms -Xmx) tried, but to no effect. Garbage collection is not an issue here, it seems. Getting various thread dumps, it looks like the system is essentially idle, but one thread, invoked by Quartz, performing some DB operation.

The relevant portion of thread dump output is:

scheduler_Worker-9 daemon prio=10 tid=0x00000000407a2000 nid=0x1cac runnable 0x00007f8bb0447000

java.lang.Thread.State: RUNNABLE

at Method)

at Source)

at com.mysql.jdbc.util.ReadAheadInputStream.fill(

at com.mysql.jdbc.util.ReadAheadInputStream.readFromUnderlyingStreamIfNecessary(


- locked <0x00000000dca645d0> (a com.mysql.jdbc.util.ReadAheadInputStream)

at com.mysql.jdbc.MysqlIO.readFully(

at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(

at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(

at com.mysql.jdbc.MysqlIO.checkErrorPacket(

at com.mysql.jdbc.MysqlIO.sendCommand(

at com.mysql.jdbc.MysqlIO.sqlQueryDirect(

at com.mysql.jdbc.ConnectionImpl.execSQL(

- locked <0x00000000dc4dac80> (a java.lang.Object)

at com.mysql.jdbc.ConnectionImpl.commit(

- locked <0x00000000dc4dac80> (a java.lang.Object)

at com.mchange.v2.c3p0.impl.NewProxyConnection.commit(

- locked <0x00000000dcabf330> (a com.mchange.v2.c3p0.impl.NewProxyConnection)

at net.sf.hibernate.transaction.JDBCTransaction.commit(

at org.springframework.orm.hibernate.HibernateTransactionManager.doCommit(



at org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(

at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(

at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(

at $Proxy89.jobToBeExecuted(Unknown Source)

at org.quartz.core.QuartzScheduler.notifyJobListenersToBeExecuted(

at org.quartz.core.JobRunShell.notifyListenersBeginning(


at com.atlassian.confluence.schedule.quartz.ConfluenceQuartzThreadPool$

at org.quartz.simpl.SimpleThreadPool$

Any ideas?

5 answers

1 accepted

This widget could not be displayed.

My issue could be resolved by not running Confluence as a normal linux user, but as root. That solved the issue and may be related to the virtualization environment, the server runs in.

This widget could not be displayed.

Seems like an expected behavior since Confluence will take some minutes to start. The amount of time to start the application will depend on the environment used, the memory given to the JDK vs the memory given to the VM and also the plugins that your Confluence has (third-party plugins).

So as a good practice, since you choose to run Confluence and the database on the same server, is important to increase the memory for the VM, so the JDK will not "starv "the operating system.

This widget could not be displayed.

My Confluence instance (running on Tomcat) regularly takes 3 to 4 minutes to completely start up.

This widget could not be displayed.

During startup my Confluence uses 100% CPU and takes around 2-3 minutes, this is normal behavior. But using 40% CPU continously doesn't seems right though...? After startup mine rarely dosen't use any CPU time, execpt when being used.

This widget could not be displayed.

Hi Axel,

As for the 40% of CPU use, I think there is something environmental going on since is not common for confluence to do this.

Maybe you can perform a quick test and try to run confluence outside the VM to verify if the problem is in the environment or not. This is a good way to narrow down the issue.

If Confluence runs smoothly outside the VM, then I recommend verifying the VM settings.

I've also had one case before in which the Tomcat was using 100% of CPU and rising the memory helped to solve the issue. Maybe you need to rise more the memory and verify how the cpu handles it.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Monday in Confluence

Why start from scratch? Introducing four new templates for Confluence Cloud

Hi my Community friends!  For those who don't know me, I'm a product marketer on the Confluence Cloud team - nice to meet you! For those of you who do, you know that I've been all up in your Co...

515 views 7 6
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