java.net.SocketInputStream.socketRead0 行: 不可用 [本地方法]

java.net.SocketInputStream.socketRead 行: 116

java.net.SocketInputStream.read 行: 171

java.net.SocketInputStream.read 行: 141

org.postgresql.core.VisibleBufferedInputStream.readMore 行: 143

org.postgresql.core.VisibleBufferedInputStream.ensureBytes 行: 112

org.postgresql.core.VisibleBufferedInputStream.read 行: 71

org.postgresql.core.PGStream.ReceiveChar 行: 272

org.postgresql.core.v3.QueryExecutorImpl.processResults 行: 1753

org.postgresql.core.v3.QueryExecutorImpl.execute 行: 348

org.postgresql.jdbc2.AbstractJdbc2Statement.execute 行: 545

org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags 行: 405

org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery 行: 285

com.alibaba.druid.pool.vendor.PGValidConnectionChecker.isValidConnection 行: 65

com.alibaba.druid.pool.DruidAbstractDataSource.testConnectionInternal 行: 1358

com.alibaba.druid.pool.DruidDataSource.getConnectionDirect 行: 1291

com.alibaba.druid.filter.FilterChainImpl.dataSource_connect 行: 4619

com.alibaba.druid.filter.FilterAdapter.dataSource_getConnection 行: 2745

com.alibaba.druid.filter.FilterChainImpl.dataSource_connect 行: 4615

com.alibaba.druid.pool.DruidDataSource.getConnection 行: 1225

com.alibaba.druid.pool.DruidDataSource.getConnection 行: 1217

com.alibaba.druid.pool.DruidDataSource.getConnection 行: 90

原因是有业务在旧数据源未失效(ip不可达)时建立了连接并等待接收数据，数据源失效后切换到新数据源，但是原来的业务仍然等待原来的连接传输数据

设置了 druidDataSource.setConnectionProperties("socketTimeout=60000;connectTimeout=5000");也不生效

Druid适应业务中途数据源ip不可达，业务自动切换到新的ip去，如何保证旧ip创建的链路被强制清理掉，不会有业务卡在等待旧连接数据传输中，这种场景如何配置Druid。