Confluence service goes down with Error 'Could not allocate space for object 'dbo.scheduler_run_details'

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Confluence experiences performance issues or might completely become unresponsive. This following error might be noted in the atlassian-confluence.logs :

1 Could not allocate space for object 'dbo.scheduler_run_details'.'PK__schedule__3213E83F5638554A' in database 'conf_prod' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.

Environment

Confluence 7.12.5

Diagnosis

The full text of the error message might look like the one below from the atlassian-confluence.logs. The Confluence instance might become unresponsive or might crash completely.

Could not allocate space object

1 2 3 4 5 [scheduler.caesium.impl.SchedulerQueueWorker] executeJob Unhandled exception thrown by job QueuedJob[jobId=LastAccessedTimeBatcherJob,deadline=1636666495952] org.springframework.jdbc.UncategorizedSQLException: Hibernate operation: could not execute statement; uncategorized SQLException; SQL state [S0002]; error code [1105]; Could not allocate space for object 'dbo.scheduler_run_details'.'PK__schedule__3213E83F5638554A' in database 'conf_prod' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.; nested exception is com.microsoft.sqlserver.jdbc.SQLServerException: Could not allocate space for object 'dbo.scheduler_run_details'.'PK__schedule__3213E83F5638554A' in database 'conf_prod' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Could not allocate space for object 'dbo.scheduler_run_details'.'PK__schedule__3213E83F5638554A' in database 'conf_prod' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.

Cause

This pattern is normally caused by non-availability of space. This could also be connected to space issues in the machine where the db is currently running.

Solution

Increase the Xms and Xms values from the setevn.sh/setenv.bat file to a higher configuration and restart the instance. If Confluence is started as a service, the heap size increase should be applied to the service. 

Updated on March 14, 2025

Still need help?

The Atlassian Community is here for you.