The culprit is almost certainly a combination of JBoss+Jetty+Jasper. Jasper is the jakarta JSP engine and has frequently been criticized for being slow. Jasper2 has been released and JBoss 3.2 should not be using it. Hopefully that will give some significant performance gains.
Also the JBoss 3.0.x series was a major functional upgrade and as such introduced a few performance issues. Many of these have been resolved in 3.2.x and I think some may be
included in 3.0.3
Finally, Jetty has been also been regaining lots of performance after it's functional upgrade to the 4.0 series. 4.1 is now the stable release and is used in
3.0.3 and 3.2. It gives a good step forward in peformance and 4.2.x series is now in development with another step.
So in short, 3.0. are probably not the fastest
JBoss releases out there. Try the 3.2 series if you want
to see better results.
I'll second this. Our testing showed similar results which have been improving very steadily with each point release. The latest and greatest is always the way to go