Advanced Deployments

JBoss AS has been tested and certified inside non-global zones in the Solaris OS. Because non-global zones behave almost identically to a normal Solaris system, no JBoss AS configuration changes need to be made to take advantage of Solaris zones. Simply copy the JBoss AS installation to the zone. You can then start JBoss AS from inside the zone as usual.

Scaling Up

As you increase the load on your server, you will likely run into some resource limits. JBoss AS has many resource pools that can be tuned according to your application needs. The Tomcat thread pool was discussed previously, but there are also many internal pools, for Message Driven Beans (MDB), for example. Many of these can be found in the configuration file $JBOSS_HOME/server/default/conf/standardjboss.xml.

If you have saturated the CPU on one server, you can continue to scale up using clustering. Simply use the all configuration and bind to a specific interface that has multicast enabled on each server. JBoss AS will automatically find the other instances on the network! There are some other considerations with clustering, such as load-balancing and session replication. Please see the JBoss High Availability and Clustering Topics web page at http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossHA for some related examples.