org.postgresql.util.PSQLException: FATAL: remaining connection slots are reserved for non-replication superuser connections

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • Here's a query you can run on PostgreSQL to check the number of connections available: {code:sql} SELECT name, current_setting(name) FROM pg_settings WHERE name = 'max_connections' {code} If this returns an insufficient number of connections, Confluence should abort start-up with a useful error message. Instead, you currently end up with exceptions occurring at runtime like this: {noformat} 2011-03-21 12:17:29,201 WARN [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0] [mchange.v2.resourcepool.BasicResourcePool] run com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@decf7d5 -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (30). Last acquisition attempt exception: -- referer: http://localhost:8080/confluence/setup/setupstandarddb.action | url: /confluence/setup/setupstandarddb.action | userName: anonymous | action: setupstandarddb org.postgresql.util.PSQLException: FATAL: remaining connection slots are reserved for non-replication superuser connections at org.postgresql.core.v3.ConnectionFactoryImpl.readStartupMessages(ConnectionFactoryImpl.java:464) at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:112) at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:66) {noformat} For those who come across this actual issue with PostgreSQL, the fix is to increase the number of connections in postgresql.conf, and adjust the shared_buffer setting as necessary too. See the [PostgreSQL documentation|http://www.postgresql.org/docs/8.2/static/runtime-config-connection.html] for more information.
    via by Matt Ryall,
  • Here's a query you can run on PostgreSQL to check the number of connections available: {code:sql} SELECT name, current_setting(name) FROM pg_settings WHERE name = 'max_connections' {code} If this returns an insufficient number of connections, Confluence should abort start-up with a useful error message. Instead, you currently end up with exceptions occurring at runtime like this: {noformat} 2011-03-21 12:17:29,201 WARN [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0] [mchange.v2.resourcepool.BasicResourcePool] run com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@decf7d5 -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (30). Last acquisition attempt exception: -- referer: http://localhost:8080/confluence/setup/setupstandarddb.action | url: /confluence/setup/setupstandarddb.action | userName: anonymous | action: setupstandarddb org.postgresql.util.PSQLException: FATAL: remaining connection slots are reserved for non-replication superuser connections at org.postgresql.core.v3.ConnectionFactoryImpl.readStartupMessages(ConnectionFactoryImpl.java:464) at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:112) at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:66) {noformat} For those who come across this actual issue with PostgreSQL, the fix is to increase the number of connections in postgresql.conf, and adjust the shared_buffer setting as necessary too. See the [PostgreSQL documentation|http://www.postgresql.org/docs/8.2/static/runtime-config-connection.html] for more information.
    via by Matt Ryall,
  • Application.properties - Front-end - GUJ
    via by Unknown author,
  • none: 10/01/2010 - 11/01/2010
    via by Unknown author,
  • SchemaSpy / Mailing Lists
    via by Unknown author,
  • Java::chat ><> & Chips - 2016-06-06 (page 1 of 2)
    via by Unknown author,
    • org.postgresql.util.PSQLException: FATAL: remaining connection slots are reserved for non-replication superuser connections at org.postgresql.core.v3.ConnectionFactoryImpl.readStartupMessages(ConnectionFactoryImpl.java:464) at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:112) at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:66)

    Users with the same issue

    Unknown visitor2 times, last one,
    Unknown User
    Unknown User2 times, last one,
    johnxfly
    johnxfly4 times, last one,
    iferca
    iferca10 times, last one,
    guizmaii
    guizmaii3 times, last one,
    18 more bugmates