• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

tomcat cross cluster communication problems

 
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi, first time posting here, but been using tomcat for a few years now.

I am running into an issue where I have 2 tomcat clusters setup, completely different servers, but for some reason, when I start memberA of clusterB, it see's memberA of clusterA and adds it as a replication node. This should not be happening, and I can't figure out why it is happening.

the setup is each cluster has 2 members in it.
Here is the snippet from the server.xml from memberA of clusterB.


On server startup, catalina.out:
INFO: Replication member added:org.apache.catalina.tribes.membership.MemberImpl[tcp://{11,11, 111, 12}:4000,{10, 27, 101, 37},4000, alive=8483725,id={-30 70 -54 46 -65 -127 76 -81 -110 104 -27 -90 35 39 124 -2 }, payload={}, command={}, domain={}, ]
The IP above, I obviously changed, but it is the IP of memberA of clusterA.

memberA - clusterA server.xml


As you can see the address and ports are completely different. Also, one weird thing, for some reason the server.xml is defined to have hte receiver port as 4000, but when I do a netstat I can see that it is listening on port 4000(which is the port that memberA clusterB is connecting to, even though neither server.xml's are stating to use port 4000)

And then even more weird, when I stop memberA on clusterB, I see the below in the logs of memberA of clusterA

INFO: Verification complete. Member already disappeared[org.apache.catalina.tribes.membership.MemberImpl[tcp://{127, 0, 0, 1}:4000,{127, 0, 0, 1},4000, alive=14572,id={-29 108 -54 -119 -110 -29 65 -128 -93 6 -104 27 -51 -106 56 51 }, payload={}, command={66 65 66 89 45 65 76 69 88 ...(9)}, domain={}, ]]

Maybe I'm missing something very easy, but I"ve been digging for a couple hours now to no avail.


 
For my next trick, I'll need the help of a tiny ad ...
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic