Win a copy of The Java Performance Companion this week in the Performance forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Tomcat Cluster Membership Question

 
Charley Watson
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm working on a Tomcat cluster configuration that uses the SimpleTcpCluster and DeltaManager -- the configuration won't allow UDP membership discovery so we've opted for the StaticMembershipInterceptor

The configuration for the interceptor looks similar on each node identifying the IP's for each member (excluding the self reference)

We're seeing odd behavior whenever a starting node is added to the cluster. The peer nodes report the membermap correctly, except the newly added node is included multiple times (see log trace below).

I think the additional nodes are incorrectly being added to the map... Would appreciate any Tomcat gurus weighing in on what they think might be happening.

Are there JMX monitors available for any of the catalina tribes implementations? Is there better trace logging available for lifecycle events relating to the tribes activity?

Any help appreciated.

when hostp05 has started and joins the membermap on hostp02:

tcp://hostp02:50001 > Enter into local membermap: tcp://hostp04:50001
tcp://hostp02:50001 > Enter into local membermap: tcp://hostp03:50001
tcp://hostp02:50001 > Enter into local membermap: tcp://hostp05:50001
tcp://hostp02:50001 > Enter into local membermap: tcp://hostp05:50001
tcp://hostp02:50001 > Enter into local membermap: tcp://hostp05:50001
tcp://hostp02:50001 > Enter into local membermap: tcp://hostp05:50001
tcp://hostp02:50001 > Enter into local membermap: tcp://hostp05:50001


salient configuration follows:




 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic