Bug 52263 - static membership cluster fails to establish membership
Summary: static membership cluster fails to establish membership
Status: RESOLVED WORKSFORME
Alias: None
Product: Tomcat 7
Classification: Unclassified
Component: Cluster (show other bugs)
Version: 7.0.23
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-29 22:55 UTC by Luke Meyer
Modified: 2012-01-12 11:59 UTC (History)
0 users



Attachments
server.xml with cluster config for node 1 (8.88 KB, text/xml)
2011-11-29 22:55 UTC, Luke Meyer
Details
Working static cluster config (3.30 KB, application/xml)
2012-01-12 11:58 UTC, Mark Thomas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Luke Meyer 2011-11-29 22:55:54 UTC
Created attachment 28003 [details]
server.xml with cluster config for node 1

I used the same cluster configuration to establish a cluster with static membership under tomcat 6.0 and 7.0. The configuration works fine under 6.0.33, but under 7.0.22 and 7.0.23 it appears that membership cannot be established; on all nodes I receive the following message for my distributed webapp:

org.apache.catalina.ha.session.DeltaManager startInternal
INFO: Register manager localhost#/petcare to cluster element Engine with name Catalina
org.apache.catalina.ha.session.DeltaManager startInternal
INFO: Starting clustering manager at localhost#/petcare
org.apache.catalina.ha.session.DeltaManager getAllClusterSessions
INFO: Manager [localhost#/petcare]: skipping state transfer. No members active in cluster group.

There are no errors or warnings; it seems the cluster just isn't formed.

I'm attaching a server.xml for one node (others are copies with obvious modifications).
Comment 1 Mark Thomas 2012-01-12 11:58:56 UTC
Created attachment 28146 [details]
Working static cluster config

I just tested this with the latest 7.0.x code and as close to your server.xml as I can replicate and I see no issues since this works for me (confirmed by using the manager app to view replicated sessions).

The Tomcat users list is the place to follow this up. Possible areas to investigate:
- the use of autobind. I'd disable this.
- network issues

For completeness, I have included the server.xml from one of my cluster nodes.