1 Reply Latest reply on Oct 1, 2011 12:42 AM by Jason Greene

    JBoss 7 questions for an upcoming JavaOne session

    Chris Kasso Newbie

      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

      22522:

       

      https://oracleus.wingateweb.com/scheduler/eventcatalog/eventCatalogJavaOne.do

       

      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

      to use.

       

      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?

       

      Thanks,

      Chris

        • 1. Re: JBoss 7 questions for an upcoming JavaOne session
          Jason Greene Master

          Chris Kasso wrote:

           

          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

          22522:

           

          https://oracleus.wingateweb.com/scheduler/eventcatalog/eventCatalogJavaOne.do

           

          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

          to use.

           

          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.

          The details are pretty long winded, but to briefly summarize we use a transactional command replication model (all configuration can be represented as commands) between domain members.

           

          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?

           

          That's correct. Also the host controller (which acts as an agent) for an installed image has to be running before it can join. (Otherwise there is nothing to talk to)

           

          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?

          No it currently does not provide a mechanism to install a new jboss image on an OS. That must be done using some other tool/process (usually specific to the OS)

           

          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?

          You mean just from the launch perspective (we have native java extension for web and messaging performance)?

           

          We have init script examples. Fedora and RHEL RPMs which include the fedora/RHEL init process are being worked on. There is an old JBoss Windows service, but it needs an update, Currently doing a windows service requires using one of the available thirdparty mechanisms.