Connection pool default behavior shift when moving from XML to YAML configuration in Codeac 2.3

Question

Goal: Identify a safe default value for the maxPoolSize setting in YAML‑based datasource configurations for Codeac 2.3 that prevents the connection pool from growing without bound under load while preserving the behavior experienced with XML configuration.
Constraints: The XML parser previously defaulted to a limit of 10 connections, but the YAML parser treats an omitted maxPoolSize as unlimited. Any new default must balance the risk of exhausting database connections against the risk of under‑provisioning the pool for varying traffic patterns, and it should be verifiable without requiring application restarts or pool resets in a test environment.
Questions: What numeric value should be adopted as the YAML default maxPoolSize to match the XML‑based default behavior? How can this default be validated across typical workloads to ensure it does not cause connection‑acquisition failures or excessive database load?

Tasadduq Burney · Answer

Answer
Set maxPoolSize: 10 in the YAML datasource configuration to replicate the XML‑based default of ten connections.
Why this works
In Codeac 2.3 the XML parser treats a missing maxPoolSize as 10, while the YAML parser treats the same omission as unlimited. Adding the explicit value restores the original ceiling.
Validation steps (no restart required)

Deploy the application with the YAML file containing maxPoolSize: 10.
Run a realistic load test (e.g., using JMeter or Gatling) that mimics peak traffic.
Monitor the pool size via JMX or the actuator endpoint (/actuator/datasource or similar). Verify that the reported active and idle counts never exceed 10.
Check connection‑acquisition latency and error rates; they should stay within baseline thresholds.
Optionally query the database (e.g., SHOW PROCESSLIST; for MySQL) to confirm total connections from the application stay ≤ 10.

What to watch for

If observed peak concurrency regularly exceeds 10, consider raising the limit after measuring actual queue length.
Deploy the change first to a staging environment to ensure no regression in connection‑acquisition failures.

Connection pool default behavior shift when moving from XML to YAML configuration in Codeac 2.3

1 answer

Answer

Why this works

Validation steps (no restart required)

What to watch for

Your perspective belongs here.

0 question comments