PUBLIC MARKS from holyver with tags doc & jboss

Now that Apache Geronimo has earned Java™ 2 Platform, Enterprise Edition (J2EE) 1.4 certification and has reached version 1.1.1, many developers will be moving away from building their software on top of more restrictive platforms. Specifically, there have been a number of articles and tutorials written lately describing migrating away from the JBoss application server to Apache Geronimo. This installment of The Geronimo renegade column describes many advantages of doing so.

Clustering allows us to run an applications on several parallel servers (a.k.a cluster nodes). The load is distributed across different servers, and even if any of the servers fails, the application is still accessible via other cluster nodes. Clustering is crucial for scalable enterprise applications, as you can improve performance by simply adding more nodes to the cluster. The JBoss Application Server (AS) comes with clustering support out of the box. The simplest way to start a JBoss server cluster is to start several JBoss instances on the same local network, using the run -c all command for each instance. Those server instances, all started in the all configuration, detect each other and automatically form a cluster. In the first section of this chapter, I discuss basic concepts behind JBoss's clustering services. It is important that you understand those concepts before reading the rest of the chapter. Clustering configurations for specific types of applications are covered after this section.

What are the advantages and disadvantages of using Tomcat embedded inside of JBoss Application Server versus running Tomcat independently?