What kind of work is Tomcat doing for each request that WAPT sends in? For example, if you were doing something that had to go back to a database, and you had a bad sync block in your code somewhere, or didn't have enough connections in your DB pool, that could cause it to behave like it is single threaded - because all of the threads / cores are contending for some shared resource.
Or, if you are just serving pages, perhaps you are disk bound, and your disk drive just isn't fast enough. Or, perhaps you have reached the limit of how much load WAPT can generate. There are lots of avenues to explore here, but they are all implementation specific. Dan --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
