Thread: [Proxool-developer] Re: Proxool behavior when max connection reached
UNMAINTAINED!
Brought to you by:
billhorsman
From: Craig S. <cs...@cr...> - 2004-05-13 13:00:04
|
Has any work been done on this. I need a similar behavior and might try to implement it, but I do not want to duplicate effort. Craig -- In theory, practice and theory are the same, but in practice they are different GPG Public Key https://www.cromagnon.com/ssl/craigkey.gpg |
From: Craig S. <cs...@cr...> - 2004-05-15 19:44:35
|
Has any work been done on this. I need a similar behavior and might try to implement it, but I do not want to duplicate effort. It seems that you would not need to more settings you would just need an allowed to wait count which if it was not 0 would make your normal limit your soft limit and then add to it for the hard limit. It looks like there are only 2 spots in the code that would need to be changed, but since the current code tries very hard not to synchronize I am not sure of the best way to do this. It would seem that if you would allow for threads to wait you would want to synchronize at that point and then notify the threads as a connection is returned. You could simply check for that feature being tunred on and only synchronize then, but you would have to make sure that if you hot change the settings to disable the waiting that you notify the waiting threads. Craig -- In theory, practice and theory are the same, but in practice they are different GPG Public Key https://www.cromagnon.com/ssl/craigkey.gpg |
From: Bertrand R. <ber...@mo...> - 2004-05-15 20:41:05
|
Thanks for your information Craig. Work has already started on this feature together with some other refactoring. I don't know yet when it will be released but part of it may be = available soon in CVS. Keep listening on proxool-dev mailing list - I'll post a message when it will start becoming available. -bertrand -----Original Message----- From: pro...@li... [mailto:pro...@li...] On Behalf Of = Craig Servin Sent: samedi 15 mai 2004 21:45 To: pro...@li... Subject: [Proxool-developer] Re: Proxool behavior when max connection reached Has any work been done on this. I need a similar behavior and might try = to=20 implement it, but I do not want to duplicate effort. It seems that you would not need to more settings you would just need an = allowed to wait count which if it was not 0 would make your normal limit your=20 soft limit and then add to it for the hard limit. It looks like there are only 2 spots in the code that would need to be=20 changed, but since the current code tries very hard not to synchronize I = am=20 not sure of the best way to do this. It would seem that if you would = allow=20 for threads to wait you would want to synchronize at that point and then = notify the threads as a connection is returned. You could simply check = for that feature being tunred on and only synchronize then, but you would = have to=20 make sure that if you hot change the settings to disable the waiting = that you=20 notify the waiting threads. Craig --=20 In theory, practice and theory are the same, but in practice they are=20 different GPG Public Key https://www.cromagnon.com/ssl/craigkey.gpg ------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now = for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id=3D2562&alloc_id=3D6184&op=3Dclick _______________________________________________ Proxool-developer mailing list Pro...@li... https://lists.sourceforge.net/lists/listinfo/proxool-developer |
From: Craig S. <cs...@cr...> - 2004-10-08 05:58:01
|
I am following up on an old thread about causing calling threads to wait for a connection rather than getting an Exception. It looks like this has not been done in CVS yet. Has anyone looked at doing this? If not, since I need the behavior, I will try to work on it. But, I do not want to repeat work so I thought I would ask before I tried to add that feature. Craig On Saturday 15 May 2004 03:40 pm, Bertrand Renuart wrote: > Thanks for your information Craig. > > Work has already started on this feature together with some other > refactoring. > I don't know yet when it will be released but part of it may be available > soon in CVS. Keep listening on proxool-dev mailing list - I'll post a > message when it will start becoming available. > > -bertrand > > > -----Original Message----- > From: pro...@li... > [mailto:pro...@li...] On Behalf Of Craig > Servin > Sent: samedi 15 mai 2004 21:45 > To: pro...@li... > Subject: [Proxool-developer] Re: Proxool behavior when max connection > reached > > > Has any work been done on this. I need a similar behavior and might try to > implement it, but I do not want to duplicate effort. > > It seems that you would not need to more settings you would just need an > allowed to wait count which if it was not 0 would make your normal limit > your > soft limit and then add to it for the hard limit. > > It looks like there are only 2 spots in the code that would need to be > changed, but since the current code tries very hard not to synchronize I am > not sure of the best way to do this. It would seem that if you would allow > for threads to wait you would want to synchronize at that point and then > notify the threads as a connection is returned. You could simply check > for > > that feature being tunred on and only synchronize then, but you would have > to > make sure that if you hot change the settings to disable the waiting that > you > notify the waiting threads. > > > > Craig |
From: <chr...@em...> - 2004-10-09 16:38:53
|
Nothing has been done so far, and your help is greatly apreciated :) You might want to draw some inspiration from the GenericObjectPool code from Jakarta, it has a configrable whenExhaustedAction: http://jakarta.apache.org/commons/pool/apidocs/org/apache/commons/pool/impl/ GenericObjectPool.html CHR > -----Original Message----- > From: pro...@li... > [mailto:pro...@li...]On Behalf Of Craig > Servin > Sent: 8. oktober 2004 07:58 > To: pro...@li... > Subject: [Proxool-developer] Re: Proxool behavior when max connection > reached > > > I am following up on an old thread about causing calling threads > to wait for a > connection rather than getting an Exception. It looks like this > has not been > done in CVS yet. > > Has anyone looked at doing this? If not, since I need the > behavior, I will > try to work on it. But, I do not want to repeat work so I > thought I would > ask before I tried to add that feature. > > Craig > > > On Saturday 15 May 2004 03:40 pm, Bertrand Renuart wrote: > > Thanks for your information Craig. > > > > Work has already started on this feature together with some other > > refactoring. > > I don't know yet when it will be released but part of it may be > available > > soon in CVS. Keep listening on proxool-dev mailing list - I'll post a > > message when it will start becoming available. > > > > -bertrand > > > > > > -----Original Message----- > > From: pro...@li... > > [mailto:pro...@li...] On > Behalf Of Craig > > Servin > > Sent: samedi 15 mai 2004 21:45 > > To: pro...@li... > > Subject: [Proxool-developer] Re: Proxool behavior when max connection > > reached > > > > > > Has any work been done on this. I need a similar behavior and > might try to > > implement it, but I do not want to duplicate effort. > > > > It seems that you would not need to more settings you would just need an > > allowed to wait count which if it was not 0 would make your normal limit > > your > > soft limit and then add to it for the hard limit. > > > > It looks like there are only 2 spots in the code that would need to be > > changed, but since the current code tries very hard not to > synchronize I am > > not sure of the best way to do this. It would seem that if you > would allow > > for threads to wait you would want to synchronize at that point and then > > notify the threads as a connection is returned. You could simply check > > for > > > > that feature being tunred on and only synchronize then, but you > would have > > to > > make sure that if you hot change the settings to disable the > waiting that > > you > > notify the waiting threads. > > > > > > > > Craig > > > ------------------------------------------------------- > This SF.net email is sponsored by: IT Product Guide on ITManagersJournal > Use IT products in your business? Tell us what you think of them. Give us > Your Opinions, Get Free ThinkGeek Gift Certificates! Click to > find out more > http://productguide.itmanagersjournal.com/guidepromo.tmpl > _______________________________________________ > Proxool-developer mailing list > Pro...@li... > https://lists.sourceforge.net/lists/listinfo/proxool-developer |
From: Bill H. <bi...@lo...> - 2004-05-13 13:12:52
|
Craig, On Thu, 2004-05-13 at 13:59, Craig Servin wrote: > Has any work been done on this. I need a similar behavior and might try to > implement it, but I do not want to duplicate effort. Work hasn't started on this, so feel free to contribute. The things to keep in mind are: 1) If hard limit = soft limit then behaviour is as it is now. Without performance impact. 2) If hard limit is reached then Proxool must refuse connections (throw SQLExceptions) as quickly as possible without too much processing. This ensures the server survives as long as possible under extremely heavy load. 3) We don't want to be creating too many threads to support this behaviour. Ideally, none at all. But if we do create any it should be a fixed amount not additional ones for each connection. If you need any help, feel free to post here. - Bill |
From: Bertrand R. <ber...@mo...> - 2004-05-13 18:02:01
|
>> Has any work been done on this. I need a similar behavior and might=20 >> try to >> implement it, but I do not want to duplicate effort. > Work hasn't started on this, so feel free to contribute. The things to keep in mind are: No 100% correct :( Have already started some work on it... And I'm close to 75% done. Not included in CVS code base yet but will be committed once 0.9 is out = (and once I got a bit more free time :( -bertrand |
From: Bill H. <bi...@lo...> - 2004-05-13 22:03:41
|
Hi Bertrand, On Thu, 2004-05-13 at 19:01, Bertrand Renuart wrote: > > Work hasn't started on this, so feel free to contribute. The things to > keep in mind are: > > No 100% correct :( Well, in my book that's good news :) Are you in a stage to share code with Craig? Would that help you out? > Have already started some work on it... And I'm close to 75% done. > Not included in CVS code base yet but will be committed once 0.9 is out (and > once I got a bit more free time :( "Once 0.9 is out".... "a bit more free time"... Hmm - Bill |