| Author |
Desynchronization between db and connection pool
|
Ashutosh Arya
Ranch Hand
Joined: Oct 07, 2008
Posts: 69
|
|
Hi,
Recently we suffered a loss of service in the dev environment caused by a "desyncronization" between connection pool and DB, that means WL thought that the active connections reached its limit (25) while in DB there was no active connections, I've mitigated it by adding a timeout parameter and a test each 60 seconds the inactive ones to test if they are alive already. This should prevent this from happening again it's a pessimistic configuration.
Do you have any hint on what could have caused this error, how to avoid it or where to look for further info?
Waiting for your response.
Thanks in advance,
Ashu
|
 |
Ashutosh Arya
Ranch Hand
Joined: Oct 07, 2008
Posts: 69
|
|
Waiting eagerly for a reply..
Regards,
Ashutosh
|
 |
anandraj tadkal
Ranch Hand
Joined: Feb 22, 2011
Posts: 80
|
|
This seems to be an issue with the Stale connections in the DB Connection pool.
Or the Connection Pool is not getting refreshed.
This could be issue with the network.
You can use an utility called dbping utility to check the connectivity.
The dbping command-line utility tests the connection between a DBMS and your client machine via a JDBC driver.
For information refer.
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/admin_ref/utils.html#wp1143071
When you enable the "Test Connections on Reserve" feature, the server instance checks a database connection prior to returning the connection to a client. This helps reduce the risk of passing invalid connections to clients.
Regards,
Anandraj
http://weblogic-wonders.com
|
Regards,
Anandraj
http://weblogic-wonders.com/
|
 |
 |
|
|
subject: Desynchronization between db and connection pool
|
|
|