This week's giveaway is in the Android forum.
We're giving away four copies of Android Security Essentials Live Lessons and have Godfrey Nolan on-line!
See this thread for details.
The moose likes Tomcat and the fly likes Tomcat Cluster Membership Question Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Products » Tomcat
Bookmark "Tomcat Cluster Membership Question" Watch "Tomcat Cluster Membership Question" New topic
Author

Tomcat Cluster Membership Question

Charley Watson
Greenhorn

Joined: Mar 19, 2005
Posts: 10
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:




 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Tomcat Cluster Membership Question
 
Similar Threads
tomcat cross cluster communication problems
Tomcat 6 Cluster Woes
JNDI in Servlets
Session ID
Tomcat and apache configuration in debian