Uploaded image for project: 'Geronimo'
  1. Geronimo
  2. GERONIMO-3759

Geronimo Tomcat Clustering - No GBeans for adding Static Members

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.1, 2.1.1
    • 2.1.3, 2.2
    • Clustering
    • Security Level: public (Regular issues)
    • None

    Description

      Tomcat uses multicasting for discovering cluster members. It also supports static memberships using the StaticMembershipInterceptor if you want to extend your membership to points beyond multicasting, using configuration as below:

      <Interceptor className="org.apache.catalina.tribes.group.interceptors.StaticMembershipInterceptor">
      <Member className="org.apache.catalina.tribes.membership.StaticMember"
      port="5678"
      securePort="-1"
      host="tomcat01.mydomain.com"
      domain="staging-cluster"
      uniqueId="

      {0,1,2,3,4,5,6,7,8,9}

      "/>
      </Interceptor>

      http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html
      http://tomcat.apache.org/tomcat-6.0-doc/config/cluster-interceptor.html

      However, to add this configuration in Geronimo's config.xml, we don't have the required GBeans for <Member> element.

      Attachments

        1. tomcat_server.xml
          8 kB
          Shiva Kumar
        2. config.xml
          31 kB
          viola.lu
        3. config_ag21.xml
          30 kB
          Shiva Kumar
        4. ClusteringStaticMembers_GERONIMO-3759.patch
          7 kB
          Shiva Kumar

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            jawarner Jason Warner
            shivahr Shiva Kumar
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment