Re: [Proxool-developer] On the number of connections in a pool during its lifetime

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

I missed the maximum conn. lifetime, which I set, by default,
to 14400000 (exactly 4 hours). The problem is that I see the
connection cleaning after the lifetime expires not every 4 hours,
but every day.
I will try to set this to lower values to see what happens.

Thanks,
Jean


bi...@lo... wrote:

>Jean,
>
>On Tue, 6 Jul 2004, Jean-Henry Berevoescu wrote:
>
>  
>
>>These are the parameters I use (connecting to a PostgreSQL database):
>>
>>proxool.maximum-connection-count 1000
>>proxool.minimum-connection-count 30
>>proxool.prototype-count 1
>>proxool.house-keeping-sleep-time 60000
>>proxool.maximum-active-time 4000
>>proxool.house-keeping-test-sql "select 0;"
>>    
>>
>
>Nothing wrong with that. I see you don't set the
>maximum-connection-lifetime so it will be the 4 hour default.
>
>Do you have any summarised log output? I'm expecting to see events showing
>that a connection had been killed because it was over 4 hours old. You
>could always set maximum-connection-count to something like 60000 (1
>minute) to see this happening more quickly.
>
>Does the connection count ever go down?
>
>- Bill
>
>
>-------------------------------------------------------
>This SF.Net email sponsored by Black Hat Briefings & Training.
>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
>digital self defense, top technical experts, no vendor pitches, 
>unmatched networking opportunities. Visit www.blackhat.com
>_______________________________________________
>Proxool-developer mailing list
>Pro...@li...
>https://lists.sourceforge.net/lists/listinfo/proxool-developer
>  
>