> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Subject: Re: Connection pooling again > > So is the enqueuing thing a bad behaviour of pooling or is it > just normal?
Your queueing problem most likely has nothing to do with the pooling capability but rather with your app, your database, or your test driver. 1) If the test driver is browser based (e.g., Java script), you're limited to two connections to a given server. If your test driver is using some generic HTTP software, that may also have the two connection limit built in, but it's less likely. 2) Does your database actually support multiple connections? Are you running into locking in the data base that's forcing serialization of requests? 3) Does your app use some sort of locking that is essentially making everything go through one request at a time? Take a thread dump during the 18-second window and see where the threads are. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
