ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit

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

Symptoms

The following error can be found on atlassian-bitbucket.log:

1 ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit

Cause

This means your Bitbucket Server instance is opening more connections than defined on your SESSIONS_PER_USER on your Oracle database

Resolution

Just as defined on Bitbucket Server config properties - DB Pool, the default value for db.pool.partition.count is 4 and db.pool.partition.connection.maximum is defined as 20 by default, the maximum number of connections to be established by Bitbucket Server will be 80 and the minimum will be 16 - as db.pool.partition.connection.minimum defaults to 4.

You could either:

  • Adjust SESSIONS_PER_USER to accommodate your current db configuration.

  • Adjust your bitbucket.properties to accommodate your SESSIONS_PER_USER

Updated on April 8, 2025
Platform
Data Center only
Product
Bitbucket Data Center
On this pageSymptomsCauseResolution

Still need help?

The Atlassian Community is here for you.
Ask the Community