ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
When DBeaver reports a hanging or timeout during SSH tunneling, the problem often lies in SSH credentials, key handling, or port conflicts. This guide walks through the recognizable symptoms, a cause table, ordered checks, targeted fixes, and when to seek escalation.
DBeaver's SSH tunnel routes database traffic through a bastion host without a VPN. Learn the correct connection settings, verification steps, and common configuration mistakes.
Learn how to set up a secure SSH tunnel in DBeaver, verify the connection, and troubleshoot common issues. This guide covers prerequisites, step‑by‑step configuration, and recovery options for both password and key‑based authentication.
Learn how to configure DBeaver’s SSH tab to create an encrypted tunnel, run queries, and avoid exposing database ports directly.
Low-Traffic Query Timeout Behavior in Hibernate Applications with infrequent database access patterns may encounter unexpected query timeout exceptions despite minimal load. Hibernate's timeout handling mechanisms, particularly when using setQueryTimeout() or hibernate.query.timeout, interact differently with connection pools and transaction managers in low-
Connection Pool Exhaustion Under Peak Load Spring Boot applications using HikariCP can experience intermittent connection pool exhaustion during peak traffic periods. The default maximumPoolSize of 10 connections may be insufficient when concurrent requests spike, causing the pool to deplete faster than connections are returned. During load testing, the appl
The goal is to guarantee that the Weblate container starts only after the PostgreSQL service is ready to accept connections, thereby avoiding the authentication error that appears when the database is not yet available or credentials mismatch. When using the official docker-compose-dev.yml, the solution must work across branches, avoid hard‑coded delays, rem
Intermittent Connection Pool Exhaustion When Phalcon is configured to use persistent PDO connections (e.g., 'persistent' => true ), high‑concurrency workloads can trigger SQLSTATE[HY000] [2002] Connection refused errors as the underlying database reaches its maximum connection limit. The framework does not expose a parameter to cap the number of persisten
MODX Revolution utilizes PDO for database interactions, typically opening a fresh connection for each request. However, the pdoPersist configuration option allows for persistent connections, which can reduce the overhead of repeated handshakes during high-traffic periods. There is uncertainty regarding the stability of persistent connections when the underly
dbeaver
r
hibernate
docker
weblate
phalcon
mysql