found another exception irregularity synchronous calls with a connection pool with only ONE node did not throw maxretry but let the original exception bubble.