Probably you are not closing connections somewhere and the maxWait property of DBCP is not set. The default is to wait indefinitely. So the tomcat is not hang, it's just waiting for a connection, but all of them are used at the moment and it keeps waiting.
I believe that if you set a maxWait parameter on your datasource configuration, you will receive a timeout error or something like this. Try to find where you are not closing the connections. Always close connections on 'finally' statements of a 'try/catch/finally' structure. Att, -- Bernardo Cattapan [EMAIL PROTECTED] On Sun, Mar 16, 2008 at 9:50 AM, ib solution <[EMAIL PROTECTED]> wrote: > hai, > > is there any an error page that you can share ?, i am using Mysql > 5.0.22 and tomcat 5.5.17 and i am always get a connection > > -- > Salam, > > Andy Susanto,S.Kom > ====================================================== > for better search > http://www.slashmysearch.com/earn/id/24828 > HP : 081513039998 > > > On Sun, Mar 16, 2008 at 4:54 PM, Mahesh Viraktamath <[EMAIL PROTECTED]> > wrote: > > Hi, > > I am using connection pooling for all the database transactions. I am > using > > the following: > > MySql: 5.0.22 > > tomcat : 5.5.X > > > > Now the problem is when I run the application, it can't get the > connnection > > from the connection pool. I tried everything like dumping all the > waiting > > threads, killing all the tomcat processes but nothing seems to work. I > can't > > revert back the results. I want to run the application as I was before. > > > > Any suggestions for closing all the connections (if open at all) or > anything > > else so that I can run mu application as earlier. > > > > Thanks in advance, > > Mahesh > > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
