It is pretty hard for anyone to comment or even help out on this. I've found that JBoss is pretty quick and most problems revolve around such things as JDBC connections, network and related areas. Without clear indication of the area of performance degradation, it is difficult to diagnose where the issue lies and how to tune the system.
If this is a rant against JBoss, then that is fine. You have been heard.
Otherwise, if you wanted a resolution, then the guys will be struggling to help. And from the posts in the forum, I'd say there are a lot of people out there happy to help.
I also have some issues as described above with jboss ... i also heard a rumour today from a company that uses jboss - only the latest version could support about 30 users concurrently.
Out of the box ... performance is pretty slow. At the moment I am trying to tweak jboss with limited results :-(
Maybe someone should post an optimization guide .. this would help alot.
There is a couple of tricks tuning CMP EJB in an article over at onJava.com (http://www.onjava.com/pub/a/onjava/2003/05/28/jboss_optimization.html)
On performance in general: http://www.doculabs.com/Downloads/WebServicePerformance_04-03.pdf
More docs are welcome, that's for sure ...
Thanks for those links, I thought by default jboss would act as a cache ie option A, silly me. Once I modified the appropriate files .. performance increased quite alot. Although still a bit sluggish .. I will try a few more tricks to push the limit ...
Once again ... thanks ..
Hello, I'm having a lot of performance issues as well. Were any of you able to find good articles about these issues? The above links did not work for me.
Best optimizations without caching are here:
SpecJ doesn't allow caching.
Use JBoss 3.2.2 and higher. A lot of performance improvements went into 3.2.2 and 3.2.3 revolving around Local interfaces, CMP, Connection Pooling. We removed almost all synchronization bottlenecks.
Also, if you're doing Entity beans, you need to look at your locking/caching strategies on a PER entity basis. There is no out-of-the-box solution for optimal performance.
One more thing, I've seen JBoss scle to much much more than 30 concurrent users on one box.
Just look at www.jboss.org. It is running all on one dual-cpu 2.4 ghz box with over 421 concurrent users. MySql is the backend running on the same machine. GetThere.com is another site running on JBoss. playboy.com is another we're in production in many many many places and if we didnt' scale beyond 30 users, nobody would use us.