Thanks Craig. That is what I have left in place this evening while I'm at home ;-) I'm just wondering what happened to these pools when they are not used all night? The connections should time out after 1/2 an hour, then what? I'm guessing they are probably going to be picked up and cleaned out as idle connections? So when I return in the morning I will find no available connections in my pool?
I guess that I could turn off the removal of idle pools, but what happens when I hit a busy period and loads of pools are used. Then I return to normal load and only a fraction are needed? I would prefer that there is some tidy up. Also, if this start up was to start 3 pools for example. These are all then leased out. I ideally would like that the pool manager opens another connection automatically, so that when I ask for a 4th connection it is there ready and waiting. So I guess I'd like come kind of minIdle config value that I could set. It's just want-want-want with me eh? Just like a little kid :D Thanks for the responses. IV -----Original Message----- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: 15 October 2002 18:17 To: Jakarta Commons Users List Subject: Re: [Pool] minimum pool size On Tue, 15 Oct 2002 [EMAIL PROTECTED] wrote: > Date: Tue, 15 Oct 2002 14:51:33 +0100 (BST) > From: [EMAIL PROTECTED] > Reply-To: Jakarta Commons Users List <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: [Pool] minimum pool size > > Afternoon chaps! > > I have just started to play with the pooling library to create a pool > (strangley enough) of connections to our acounting package. This is > using the Java to COM bridge and creating objects in this takes forever, > hence the need for a pool. > > The problem I have is that the creation of my objects that I pool takes > a long time, and I'd like to create them in advance of their use. > However, I can't find anything like a minimum number in the pool (as > there is with the maximum value) Therefore, the first time that an > object is requested it still has to be created. > > Any help is much apreciated. I've tried to look through the archives, > without any success! > This workaround sounds so simple that there must be something wrong with it :-), but how about this: in the startup logic of your application, just create a loop that requests the appropriate number of instances of your connection object (without returning them), followed by returning them all. That way, the pool will have the preconfigured instances available by the time your application actually starts using them. > regards > IV > Craig -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
