From: Jean-Henry B. <ber...@ne...> - 2003-05-04 03:01:24
|
Hi, I have a little problem and it might be due to some seeting I overlook. I want to maintain the valid connections alive and only kill the faulty ones. In my setup it happens to get SQL statements that block for seemingly unlimited time and I'd like to close only the connections having preoblems like these. Proxool works for me all right in all the respects, but it keeps closing my connections that are older than the (default or programatically set) "maximum-active-time". From the documentation I learned that I can use the "house-keeping" facility in order to kill invalid connections. So I set "house-keeping-sleep-time" to, say, 5 seconds and I also have "house-keeping-test-sql" set to a valid light-weight SQL query. But all these do not help - proxool keeps killing all the connections no matter what and it keeps the "invalid" ones. I will be very happy if I could use a call to a version of "reallyClose()" method (and forget about all the settings I talked about) - since I have a way to detect the "faulty statements" in my program, but "reallyClose()" is unusable from outside the Proxool packages. Any tips on these problems will be highly appreciated. Thanks, Jean |