on 01-29-2009 4:20 PM
I have a datasource setup in the JDBC Connector service through Visual Administrator. When a connection becomes invalid, for example due to a network problem, the connection remains in the pool. When requesting a connection, my application still receives the invalid connection and it seems that the J2EE engine never takes the bad connection out of the pool. We have to stop and restart the Datasource via the JDBC Connector service to resolve the issue.
Is there a way to make the connector service validate and remove bad connections?
I have found note #1030259 which answers this. We have our datasource set to "Vendor SQL". By switching to "Native SQL", a broken connection is removed from the pool then next time it is accessed, which provides recovery without having to restart the entire datasource.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.