Article DetailsDetailsHelp DetailsWhen the number of connections to your Aura (AuraDB and AuraDS) Instance exceeds a certain level, you might see the below error: Neo4jError: There are no available threads to serve this request at the moment. You can retry at a later time or consider increasing max thread pool size for bolt connector(s). We recommend getting yourself familiar with thread pool size. As there could be a high number of idle connections, you should set withMaxConnectionPoolSize to an optimal number in the driver objects. The default setting for maxConnectionPoolSize is 200. If you are connecting from just one driver instance, the default value would be fine.But If you have multiple instances of your application or if you are initializing multiple driver instances within the same application, the default maxConnectionPoolSize value of 200 could quickly multiply and overwhelm your Aura instance. The suggested setting for withMaxConnectionPoolSize is 20, and it can be tuned the value based on the setup and load on the Aura Instance. Config config = Config.builder() .withMaxConnectionLifetime( 30, TimeUnit.MINUTES ) .withMaxConnectionPoolSize( 20 ) .withConnectionAcquisitionTimeout( 2, TimeUnit.MINUTES ) .build(); Driver driver = GraphDatabase.driver( uri, AuthTokens.basic( user, password ), config ); The maximum number of connections an Aura instance can handle would depend on the type (Free or Professional/Enterprise, AuraDB or AuraDS) of the instance.Please read How to operate with many applications connecting to my AuraDB Instance using the driver (maximum connections)? to understand this better. InformationTitleNeo4jError: There are no available threads to serve this request at the moment.Article Created Date3/15/2024, 10:57 PMURL Name4407446541459-Neo4jError-There-are-no-available-threads-to-serve-this-request-at-the-momentLast Modified Date9/7/2026, 6:49 AM