It's not a matter of web connection, the server listen with serverSocket on a port, so i made a test application that connect with 30 threads.
What i can't understand is: connection pooling shouldn't perform 'x' concurrent connections? Why instead enqueue it? Is it because i do from same ip (mine)? ---------- Initial Header ----------- >From : "Caldarale, Charles R" [EMAIL PROTECTED] To : "Tomcat Users List" users@tomcat.apache.org Cc : Date : Wed, 9 Apr 2008 06:18:40 -0500 Subject : RE: Connection pooling again > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Subject: Connection pooling again > > > > i think i don't get the utility of a connection pooling, > > since i have this situation: 30 threads try to perform at > > same time a db access with the call: > > Are you running the 30 client requests from a single browser? If so, > you are likely hitting the HTTP RFC recommended limit of two concurrent > connections to a given server. You can tweak browser settings to raise > the limit, or try it with a more appropriate testing tool. > > - 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] > > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
