proxool-developer

[Proxool-developer] Proxool settings

[Jean-Henry B. <ber...@ne...>]

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

Re: [Proxool-developer] Proxool settings

[Jean-Henry B. <ber...@ne...>]

Hi,
I found the problem: it was happening with some connections I was not
properly releasing. Sorry for the missunderstanding.

Jean



Jean-Henry Berevoescu wrote:

>
> 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
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Proxool-developer mailing list
> Pro...@li...
> https://lists.sourceforge.net/lists/listinfo/proxool-developer
>

-- 
Your favorite stores, helpful shopping tools and great gift ideas. 
Experience the convenience of buying online with Shop@Netscape! 
http://shopnow.netscape.com/

Re: [Proxool-developer] Proxool settings

[Bill H. <bi...@lo...>]

Hi Jean,

On Mon, 2003-05-05 at 00:31, Jean-Henry Berevoescu wrote:

> I found the problem: it was happening with some connections I was not
> properly releasing. Sorry for the missunderstanding.

No problem. I was just composing my reply to your original mail. I have
some comments to make anyway :)

> I'd like to close only the connections having problems

You kind of can do this using:

ProxoolFacade.killConnection(alias, id, merciful);

But you need to know the connection ID for that to work and that's not
immediately available to you. I guess we probably need a method like:

ProxoolFacade.killConnection(connection, merciful);

(As a reminder, the merciful parameter allows you to decide whether to
kill the connection immediately (merciless) or when it is next inactive
(merciful).

I think I will add that method for the next release.

> > Proxool ... keeps closing my connections that are older than the 
> > "maximum-active-time". 

More accurately, connections that are active without having been closed
properly and are old than this time.

> > 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.

Yes, the house keeper only tests inactive connections. During busy
times, this means that some connections might not get tested for several
sweeps of the house keeper.

Let me know if you have any other queries.

Cheers,
Bill