Thanks, I'll do that, but still - how can I be sure that my pool have more than just this one connection. Writing two servlets with endless loops, avoiding checking the connections back would give me the answer I guess. But why is there only one connection established to my DB server??
Is there a way to configure the pool to pre generate eg. 10 connections? \trond -----Original Message----- From: Kyle [mailto:[EMAIL PROTECTED] Sent: 23. september 2005 02:14 To: Tomcat Users List Subject: Re: db-connectin is working fine, but is it pooling? Print out your Connection Object .toString() to stdout or on a page and you should see that it is a Pool(ed|able) Connection object. K Trond Hersløv wrote: >Everything works just fine, but I'm a little bit concerned that maybe I am >generating a singel connection to the DB and not a pool of connections. >As I run netstat -a on the machine hosting the DB, I expected to find >a lot of connections to port 3306, which my MySQL server listens to, but there >is only one single connection. Even when I press F5 for a long time to refresh >my IE window like a 100 times or with more windows open at the same time there >is just this one connection to be found. > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ********************************************************************** This email message has been swept by MIMEsweeper for the presence of computer viruses. ********************************************************************** --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
