Hi Rainer. Thank you very much for this preliminary information. I had already noticed the AbandonedObjectPool messages myself.
My resource configuration: name="bam/jdbc/vip8db" auth="Container" type="javax.sql.DataSource" username="***REMOVED***" password="***REMOVED***" driverClassName="com.microsoft.jdbc.sqlserver.SQLServerDriver" url="jdbc:microsoft:sqlserver://***REMOVED***;databasename=***REMOVED***" removeAbandoned="true" removeAbandonedTimeout="60" logAbandoned="true" validationQuery = "SELECT Bedrijfscode FROM entBedrijf" I have already checked the Java code of the first 4 or 5 waiting threads, but all connections/statement/resultsets are correctly closed. So the problem seems to be in the dbcp, as you already say. But I'm not sure yet. Would there be some kind of quick fix for now? To prevent Tomcat from hanging? Although of course I'd prefer a real solution.. Thank you very very much for your work so far. I hope we will get to the solution! Jesse. Rainer Jung-3 wrote: > > The root problem lies within the database connection pool. All 400 > Tomcat threads are waiting in getConnection() to get a free DB > connection from the common-dbcp pool. > > There are some bugs around dbcp, but I need a little time to check, if > they apply to your version. This is just a short note, that yes, there > is some hope ;) > > In the meantime: could you post your DataSource configuration (omit the > password). > -- View this message in context: http://www.nabble.com/IIS-6.0---JK1.2.25---Tomcat-5.5.20---%22Service-temporary-unavailable%22-tp18238896p18256392.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
