This week's book giveaway is in the OCPJP forum. We're giving away four copies of OCA/OCP Java SE 7 Programmer I & II Study Guide and have Kathy Sierra & Bert Bates on-line! See this thread for details.
Is there a way to run a smaller footprint (less disk space, less memory, less CPU) of JBoss with stripped down functionality?
In particular I'm thinking of client apps in the context of web services that might themselves be servers, but not servers that would be receiving many hits and certainly wouldn't need all of the functionality of JBoss.
You can prune down the footprint substantially but it takes a lot of experimentation. The obvious thing is to throw stuff away from the deploy directory, but it also matters to remove things from the lib directory as well, and pay attention to stuff mentioned in files in the conf directory. Even services you keep can be pruned down by reducing unwanted interceptors. At the end of the day you'll only know if you got it right when your server *and* your application can still run. Some services don't kick in that much at startup.
Reid - SCJP2 (April 2002)
Joined: Aug 22, 2005
It would be really interesting to have an app that would watch your web application execute and determine which portions of JBoss are used and which ones are not needed. I wonder if some of the dependency tools might be able to do something like that. It's kind of difficult to determine where to spend your time to get to that perfect footprint quicker.