We are developing a session for JavaOne this year titled:
Java EE Cluster Management Strategies
The purpose of this session is to discuss various Java EE cluster
management strategies and to provide a survey of which strategies
popular application servers are using today.
You can read the entire abstract for the session by looking up session
This will be a product neutral talk focusing on what the various
management strategies are and less on how any particular product implements
them. But we will also provide a survey of existing products (WebSphere,
JBoss, GlassFish, WLS, Resin, etc) to show which strategy each has chosen
In order to create an accurate survey we are reaching out to the
experts for various products. We have reviewed the JBoss documentation
but have some questions about JBoss 7. Hopefully there is an expert
or two who can assist.
Here's the questions:
How are configuration changes replicated from the Domain Controller to
the server instances? For example shared storage, sending config changes
to node agents, replicating commands to instances, etc.
Does JBoss support any form of redundancy of the Domain Controller? For
example with Resin they support a "triad" of admin servers that handle
administration of the instances. GlassFish has no redundancy but instances
continue to run without problem if the DAS goes down. I assume that
is also true with JBoss.
I assume that from the Domain Controller you can create/delete
as well as start/stop instances running on a remote node assuming
JBoss is already installed on the remote node?
Can the Domain Controller be used to provision hosts that will manage
new instances? For example, suppose a cluster is going to be expanded by
adding additional instances. Before the Domain Controller can configure
the instance for use in the cluster the someone or something must install
a copy of JBoss on the target system. Does the Domain Controller provide
a way to provision the JBoss software on the target system?
Does JBoss offer any native OS integration e.g. running the instance or
host controller as a Windows Service or starting from init.d on Unix?