A Spring Boot service's `/actuator/health` endpoint reports UP, but the service is actually unable to process real requests due to an exhausted database connection pool.

This indicates the health check isn't deep enough — a basic 'is the process alive' check passes while the actual dependency the service needs (an available DB connection) is exhausted. Fix by ensuring the health/readiness endpoint includes the database health indicator (Actuator does this automatically if the DB health indicator is enabled and not explicitly excluded) so pool exhaustion is correctly reflected as not-ready rather than falsely healthy.