Connection Refresh Delay

[jrenck]

I'm using JndiObjectFactoryBean and JdbcTemplate to access my datasources managed by a Weblogic 8.1 and Oracle 8.1/9. The problem is that whenever the connections are lost the first guy that hits a resource that depends of those connections has to wait for the connection timeout and then the time to get a new one something that is very annoying. Do you know anyway to avoid this to happen?

Thanks,

Johann

[karldmoore]

On connection pools like c3p0 and DBCP there are various testOn* settings you can use. I'd presume your connection pool would have the same kind of setting.

[jrenck]

The weblogic's connection pools have all the test options but the problem is that if at the moment when you are trying to use a connection they are all dead you are going to have to wait for the connection timeout and then for the time that takes to get a new one from the connection pool. I was thinking about generating a daemon to check via JNDI or JMX the status of the connections and force a refresh if they are dead but before going this way I was trying to find another solution via Spring, any ideas?

Thanks,

Johann

[jrenck]

From the jdbc dev2dev forum:

"The pool can be configured to test connections periodically independent of
user load, and will replace bad ones if the DBMS is still up and available.
This would prevent later incoming user requests from having to wait.
Joe"

So that solved the problem.

Cheers!

Johann

[karldmoore]

Glad you found a solution, is a possible to post the link? Might help others in future.

[jrenck]

There you go
http://forums.bea.com/bea/thread.jsp...18496 0156752

Johann

[karldmoore]

Thanks Johann hopefully this might be useful for other people in the future .