R2DBC Request Timeouts during IDE Services activation – Support | JetBrains

Problem

During an IDE Services activation process, R2DBC requests sent to the database could fail due to a timeout. It causes license activation failure and prevents further usage of the product.

IDE Services log shows next errors:

2026-02-03T09:47:14.096Z ERROR 1 --- [IDE Services 2025.6.1.6568] [tp1826026740-81] requestLog                               : unhandled exception: org.springframework.dao.DataAccessResourceFailureException: Failed to obtain R2DBC Connection
 at org.springframework.r2dbc.connection.ConnectionFactoryUtils.lambda$getConnection$0(ConnectionFactoryUtils.java:102)
...2026-02-03T10:19:26.001Z ERROR 1 --- [IDE Services 2025.6.1.6568] [qtp149814534-81] requestLog                               : unhandled exception: org.springframework.dao.DataAccessResourceFailureException: Failed to obtain R2DBC Connection
Suppressed: java.lang.Exception: #block terminated with an error
...
Caused by: io.r2dbc.spi.R2dbcTimeoutException: Connection acquisition timed out after 30000ms
Caused by: java.util.concurrent.TimeoutException: Did not observe any item or terminal signal within 30000ms in 'Connection acquisition from [org.springframework.boot.r2dbc.OptionsCapableConnectionFactory@2af87d7a]' (and no fallback has been configured

Cause

Issue is environment-specific and can be caused by OS-level firewall, network configuration ot built-in cryptography libraries which could possibly affect the license activation token.

Workaround

Try the following to mitigate the issue:

Make sure the SELinux is disabled
Try to stop firewall too if enabled: sudo systemctl stop firewalld
If previous steps didn't help, add the following Java Tool Option to the IDE Services configuration file: -Djava.security.egd=file:/dev/./urandom.

For docker-based deployments, it can be added as the part of environment variable like

ide-services:
  environment:
       - JAVA_TOOL_OPTIONS=-Djava.security.egd=file:/dev/./urandom

For Linux service deployment, you need to add JAVA_TOOL_OPTIONS as environment variable so it is fetched by the application.

Also, consider upgrading to CentOS 9 / RHEL 9 from 8s versions to mitigate the issue as it's not reproduced with them.