Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of stewart.vince@gmail.com
 designates 209.85.128.48 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CABOBwRjf2kSRCn6wSC++DE840WgyAVbfhQ-DybsRyCf0Sb13Qw@mail.gmail.com>
References: 
 <CABOBwRi4be_MnbSO7zNBZX9VVioyGU-ZarcWQBD5wJWkXOOO8Q@mail.gmail.com>
	<42B9B997-E1EF-4C24-A3A1-48A4D704ABB5@j-b-s.de>
	<CABOBwRhTYP0QPeqaVNKE=9+TJcjS5nbtXj4bFJ7y+RPzFFNzmA@mail.gmail.com>
	<51D3270F.8090906@christopherschultz.net>
	<CABOBwRgVg2qqGNVzQg7nW+NkzU+3XgF7kFeEAxORnfzsUn9mjQ@mail.gmail.com>
	<CAO5YfeRk4nk0AYOAHo03mVHRVhbH79QPLT9AGz1iZa_C6PN=sg@mail.gmail.com>
	<CABOBwRjf2kSRCn6wSC++DE840WgyAVbfhQ-DybsRyCf0Sb13Qw@mail.gmail.com>
Date: Thu, 4 Jul 2013 10:14:38 +1200
Message-ID: 
 <CAO5YfeS7aBd0O2F15hH6CE2RJRQJvJAMEyugs9Ax=E9L3vG9ow@mail.gmail.com>
Subject: Re: Share info across different sessions & servers
From: Vince Stewart <stewart.vince@gmail.com>
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: multipart/alternative; boundary=047d7bea4484982a3704e0a2c9f0

--047d7bea4484982a3704e0a2c9f0
Content-Type: text/plain; charset=ISO-8859-1

Hi Jose,

a couple of things,
1) I use embedded Tomcat to build my application and this has allowed me to
maintain 2 single-line patches in tribes classes by adding tribes source
code to my compilations. However those patches are only necessary with
large messages that take more than 3 seconds to be transmitted from the
transmitting machine to the Internet Service Provider machine (approx 0.5
meg for my system). There is a config setting (Sender/Transport/timeout)
that's supposed to alter this 3 second timeout limit but I'm not sure it
works.
2) The implementation is not at all trivial. You have to register
StaticMember objects because usual member discovery does not work over
wide-area network (WAN). I allocate one machine as "SuperServer" and all
other machines have to enroll with SuperServer at startup. All machines
need to have a unique combination of Ipv4 address and port number (which
might represent a redirection port for use by the router whereupon
networked machines also need LAN addresses set). Once registration is
complete, all sub-Server machines can send/receive SuperServer and vice
versa.

There is a tutorial on-line which is adequate but not for WAN. I think you
have at least two weeks of work in front of you using tribes but I am very
happy I used this method.
None of my code would add much (except confusion) to that in the tutorial.
Make sure you start without multicast enabled as it currently is suitable
only for LAN.

 ///Class Constructor
 public ServerMessaging() throws SocketException{
 this.myChannel=new GroupChannel();
 ChannelListener msgListener = new ServerMessaging.MyMessageListener();
 MembershipListener mbrListener = new ServerMessaging.MyMemberListener();
 myChannel.addMembershipListener(mbrListener);
 myChannel.addChannelListener(msgListener);
  try{

myChannel.start(Channel.MBR_TX_SEQ|Channel.MBR_RX_SEQ|Channel.SND_TX_SEQ|Channel.SND_RX_SEQ);//no
multicast
  }
  catch(ChannelException e){
  U.log(e);
  }
 }

public void detectOrderNumber_EnrollWithSuperServer() throws
ChannelException{
setMyServerOrderStatus(); // machine reads its mac address or some file;
then from a table will set serverOrderNumber to 0 for superserver ; others
1,2,3...
 if(this.getServerOrderNumber()==0){  ////meaning this is the superserver
 someObject.doSomeThingMaybe();
 }
 else{
 this.sendAckRequiredMessage(0,"Enrollment"); /// first argument specifies
SuperServer, member 0 (a table will need to be provided to hold IPv4
address and port for each member)
 }
}

--047d7bea4484982a3704e0a2c9f0--