I don't know if this will help anybody else, but: If you've got a large code-base, and it encompasses various java projects and whatnot, you'll see a significant speed/memory boost to JBoss if you disable the "automatic" EJB3 detection stuff in the EJB3 deployer.
If you're running into a lot of "out of permGen" memory errors when starting your instance, this could be the culprit. I was able to move from 1024 to 512 megs of permspace, after changing the deployment setting. This sucker (JBoss 5 beta 4) starts up in 30 seconds, vs. >2 minutes, now too. You can still use EJB3 / annotations stuff, but you have to specifically enable it in a case by case basis. Probably 99% of people won't even have this problem, but if this helps %1, right on. I discovered it while tuning/slimming a server instance for development purposes. I'm very happy with what I've ended up with. It's solid. that's about it, I reckon. -den -- "When a distinguished but elderly scientist states that something is possible, he is almost certainly right. When he states that something is impossible, he is very probably wrong." - Arthur C. Clarke ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;192386516;25150098;k Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:307058 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
