Confluence fails to process index queue automatically

Still need help?

The Atlassian Community is here for you.

Ask the community

This content applies only to Confluence 5.5 and earlier. Versions 5.6 or later do not use the indexqueueentries table nor do they have the .timestamp file.

The indexing of documents can also fail if there are database errors or the queue is stuck. For Confluence 5.6 - 5.9.3 please check Scheduled jobs may stall and fail to process if one job becomes stuck for more analysis and resolutions.


  • Newly added content is not picked up by Confluence Search.
  • The Recently Updated list is not showing new entries.
  • New blog posts are not shown or displayed in the Blog Posts Macro
  • When Lucene Debug log is enabled it shows Confluence tried Fetching index entries added in the future, something like this:

    or this:
  • If the following appears in the atlassian-confluence.log, proceed to Alternative Cause and Resolution sections:

    2014-05-04 11:50:28,863 ERROR [scheduler_Worker-3] [org.quartz.core.ErrorLogger] schedulerError Unable to notify JobListener(s) of Job to be executed: (Job will NOT be executed!). trigger= DEFAULT.IndexQueueFlusher job= DEFAULT.IndexQueueFlusher
    org.quartz.SchedulerException: JobListener 'ScheduledJobListener' threw exception: Could not open Hibernate Session for transaction; nested exception is net.sf.hibernate.exception.GenericJDBCException: Cannot open connection [See nested exception: org.springframework.transaction.CannotCreateTransactionException: Could not open Hibernate Session for transaction; nested exception is net.sf.hibernate.exception.GenericJDBCException: Cannot open connection]
    	at org.quartz.core.QuartzScheduler.notifyJobListenersToBeExecuted(
    	at org.quartz.core.JobRunShell.notifyListenersBeginning(
    	at com.atlassian.confluence.schedule.quartz.ConfluenceQuartzThreadPool$
    	at org.quartz.simpl.SimpleThreadPool$
    Caused by: org.springframework.transaction.CannotCreateTransactionException: Could not open Hibernate Session for transaction; nested exception is net.sf.hibernate.exception.GenericJDBCException: Cannot open connection
    	at org.springframework.orm.hibernate.HibernateTransactionManager.doBegin(
    	at org.springframework.transaction.interceptor.TransactionAspectSupport.createTransactionIfNecessary(
    	at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(
    	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
    	at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(
    	at com.sun.proxy.$Proxy104.jobToBeExecuted(Unknown Source)
    	at org.quartz.core.QuartzScheduler.notifyJobListenersToBeExecuted(
    	... 4 more
    Caused by: net.sf.hibernate.exception.GenericJDBCException: Cannot open connection
    	at net.sf.hibernate.exception.ErrorCodeConverter.handledNonSpecificException(
    	at net.sf.hibernate.exception.ErrorCodeConverter.convert(
    	at net.sf.hibernate.exception.JDBCExceptionHelper.convert(
    	at net.sf.hibernate.impl.BatcherImpl.convert(
    	at net.sf.hibernate.impl.BatcherImpl.openConnection(
    	at net.sf.hibernate.impl.SessionImpl.connect(
    	at net.sf.hibernate.impl.SessionImpl.connection(
    	at org.springframework.orm.hibernate.HibernateTransactionManager.doBegin(
    	... 11 more
    Caused by: java.sql.SQLException: Connections could not be acquired from the underlying database!
    	at com.mchange.v2.sql.SqlUtils.toSQLException(
    	at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(
    	at com.mchange.v2.c3p0.impl.AbstractPoolBackedDataSource.getConnection(
    	at net.sf.hibernate.connection.C3P0ConnectionProvider.getConnection(
    	at net.sf.hibernate.impl.BatcherImpl.openConnection(
    	... 14 more
    Caused by: com.mchange.v2.resourcepool.CannotAcquireResourceException: A ResourcePool could not acquire a resource from its primary factory or source.
    	at com.mchange.v2.resourcepool.BasicResourcePool.awaitAvailable(
    	at com.mchange.v2.resourcepool.BasicResourcePool.prelimCheckoutResource(
    	at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(
    	at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(
    	... 17 more


Check the <confluence data folder>/index/.timestamp file to see if it is dated in the future.


Check the table indexqueueentries with:

select * from indexqueueentries;


And verify if there is any date future from todays date or time.


Confluence will fetch and sort the last modified date from every content and put them in the index queue. It compares the last modified date against the current date. If you have one or more item in your content that is future dated this will cause the operation to fail. See also  CONF-21720 - Getting issue details... STATUS .

First Alternative: There's not enough database connection pool to be utilised for automatic (scheduled) index flushing.

Second Alternative: The vm hosting Confluence is in Pause mode.


Flush the index queue or rebuild the index, as described in Content Index Administration.


tip/resting Created with Sketch.

Note that the more common cause for this issue is Recently Updated, Mail, or Search not functioning.

To resolve this problem,

  1. Shutdown Confluence and make a database backup.
  2. Find the future dated content in the CONTENT table and change it:

    select * from CONTENT where lastmoddate like '2010-10-01%';

    (info) In our example the content was future dated to 2010-10-01. You need to change the query to your own based on your debug log file.

    Another tip to easily figure out this is to use current date/time function of database SQL query. For example, in MySQL you could run this query:

  3. Change the lastmoddate value in your database:

    update CONTENT
    set lastmoddate = '2009-10-01 09:08:13.253'
    where contentid = <contentid>;

    (warning) Important: change the lastmoddate value to one that is appropriate to your case.
    (info) <contentid> is contentid value returned from the first query.

    Another tip to easily change all the affected contents' lastmoddate is to use the date/time function as described in the above info box. For example, in MySQL you could run something like this:

  4. Clear your INDEXQUEUEENTRIES table:

    delete from INDEXQUEUEENTRIES;
  5. If you have plugin or edge directory under your <confluence home>/index directory, please back them up first to somewhere safe. Then delete your <confluence home>/index directory.
  6. Restart Confluence and rebuild your index.
  7. After Confluence has completed building it's index to 100%, try to add a new page and check if that gets indexed / not - confirm that the <confluence data folder>/index/.timestamp file is created with the right time.

First Alternative

Second Alternative

  • Restart the VM hosting Confluence or take it out of Pause mode















Last modified on Nov 15, 2018

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.