> 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. >
No, my test is done with threads that connect using sockets. Server listen with ServerSocket and 30 Threads are started connecting to it. > 2) Does your database actually support multiple connections? Are you > running into locking in the data base that's forcing serialization of > requests? > Since i'm not the owner of the db part, how can i check it? what should i ask to check to the db admin? > 3) Does your app use some sort of locking that is essentially making > everything go through one request at a time? > No, synchronized block are removed from that part, so there should not be any concurrency limitation on that side > Take a thread dump during the 18-second window and see where the threads > are. > How? Should i use Jconsole.exe program? > - Chuck > thanks --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
