>The Tomcat thread pool is finite; we'll call the maxThread value T. Likewise, the db connection pool is finite, and we'll call its size D. The client makes some number of requests that are not committed, which we'll label R. Anytime R > T + D, you're stuck.
Yes - that's my understanding of the problem. But as I change D (my db connection pool size) and R, Tomcat's maxThread value (T) seems to be very small (1 or 2). That surprised me, and led me to think something else was going on here. -- View this message in context: http://www.nabble.com/Tomcat-thread-pool-question-tp20915752p20941231.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
