# Problem with JDBC Pool

**URL:** <https://forums.percona.com/t/problem-with-jdbc-pool/3204>\
**Category:** Percona XtraDB Cluster 5.x\
**Created:** [January 15, 2014, 4:58am UTC](https://forums.percona.com/t/problem-with-jdbc-pool/3204 "2014-01-15T04:58:58Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![marcom1981](https://avatars.discourse-cdn.com/v4/letter/m/f14d63/32.png) [@marcom1981](https://forums.percona.com/u/marcom1981)\
**Post date:** [January 15, 2014, 4:58am UTC](https://forums.percona.com/t/problem-with-jdbc-pool/3204/1 "2014-01-15T04:58:58Z")

</div>

Hello,  
My company is considering Percona cluster in order to improve our service.  
We’re running some tests with the drive-mode loadbalance with JDBC connection pool.

We have the following problem:  
When stopping a node, the node connections in the pool return error.

Is there a way to prevent these connections may return error and maybe connections to migrate to another node in a transparent manner for the clinet.

We use this connection string:  
jdbc:mysql:loadbalance://pte-ngdb1.pte.actalis.it,pte-ngdb2.pte.actalis.it,pte-ngdb3.pte.actalis.it/test\_cluster?loadBalanceBlacklistTimeout=5000

Thanks in advance.