Resolution:
Description:
============
In TIBCO BusinessEvents , how to run the Oracle Coherence Multicast Test ?
    Or
How to test Oracle Coherence Multicast Communication between two machines ?



Environment:
==========
TIBCO BusinessEvents 3.x
  

Resolution:
==========
Running/Testing Fault Tolerance between two different machines.

--------------------------------------------------------------



1). First run the multicast test between two machines to check if multicasting between them is working properly.

For running multicast test, follow the steps below.

a). Set "coherence.jar" and "tangosol.jar" in the classpath on both machines.
    
  b). Type and Enter "java com.tangosol.net.MulticastTest -group 224.3.1.1:31341" at
        the command prompt of first machine.You will see something like the following:
              
         Starting test on ip=msaurabh-T61/10.105.96.85, group=/224.3.1.1:31341, ttl=4
         Configuring multicast socket...
         Starting listener...
         Thu May 15 13:38:03 PDT 2008: Sent packet 1.
         Thu May 15 13:38:03 PDT 2008: Received test packet 1 from self (sent 16ms ago)
          Thu May 15 13:38:05 PDT 2008: Sent packet 2.
          Thu May 15 13:38:05 PDT 2008: Received test packet 2 from self
          Thu May 15 13:38:07 PDT 2008: Sent packet 3.
          Thu May 15 13:38:07 PDT 2008: Received test packet 3 from self
          Thu May 15 13:38:09 PDT 2008: Sent packet 4.
          Thu May 15 13:38:09 PDT 2008: Received test packet 4 from self
          Thu May 15 13:38:11 PDT 2008: Sent packet 5.
          Thu May 15 13:38:11 PDT 2008: Received test packet 5 from self
              ..................


   c). At command prompt on the second m/c, type and enter "java com.tangosol.net.MulticastTest -group 224.3.1.1:31341"
              
       You will something like the following:              

        Starting test on ip=P4-SMITTAL/10.105.96.148, group=/224.3.1.1:31341, ttl=4

        Configuring multicast socket...
        Starting listener...
        Thu May 15 13:40:49 PDT 2008: Sent packet 1.
        Thu May 15 13:40:49 PDT 2008: Received test packet 1 from self (sent 16ms ago).
        Thu May 15 13:40:50 PDT 2008: Received test packet 5 from ip=msaurabh-T61/10.105.96.85, group=/224.3.1.1:31341, ttl=4.
        Thu May 15 13:40:51 PDT 2008: Sent packet 2.
        Thu May 15 13:40:51 PDT 2008: Received test packet 2 from self
        Thu May 15 13:40:52 PDT 2008: Received test packet 6 from ip=msaurabh-T61/10.105.96.85, group=/224.3.1.1:31341, ttl=4.
         Thu May 15 13:40:53 PDT 2008: Sent packet 3.
         Thu May 15 13:40:53 PDT 2008: Received test packet 3 from self
         Thu May 15 13:40:54 PDT 2008: Received test packet 7 from ip=msaurabh-T61/10.105.96.85, group=/224.3.1.1:31341, ttl=4.
          Thu May 15 13:40:55 PDT 2008: Sent packet 4.
              ..................                

                                

   d). Goto the first m/c command prompt and you will see something like the following:            
          Thu May 15 13:40:52 PDT 2008: Received test packet 6 from self
          Thu May 15 13:40:53 PDT 2008: Received test packet 3 from ip=P4-SMITTAL/10.105.96.148, group=/224.3.1.1:31341, ttl=4.
          Thu May 15 13:40:54 PDT 2008: Sent packet 7.
          Thu May 15 13:40:54 PDT 2008: Received test packet 7 from self
          Thu May 15 13:40:55 PDT 2008: Received test packet 4 from ip=P4-SMITTAL/10.105.96.148, group=/224.3.1.1:31341, ttl=4.
          Thu May 15 13:40:56 PDT 2008: Sent packet 8.
          Thu May 15 13:40:56 PDT 2008: Received test packet 8 from self
          Thu May 15 13:40:57 PDT 2008: Received test packet 5 from ip=P4-SMITTAL/10.105.96.148, group=/224.3.1.1:31341, ttl=4.
          Thu May 15 13:40:58 PDT 2008: Sent packet 9.
          Thu May 15 13:40:58 PDT 2008: Received test packet 9 from self
          Thu May 15 13:40:59 PDT 2008: Received test packet 6 from ip=P4-SMITTAL/10.105.96.148, group=/224.3.1.1:31341, ttl=4.
          

          
This test confirms that multicast is enabled between the two machines. If you are unable to establish bidirectional multicast communication try the following:
        

Firewalls : If any of the machines running the multicast test are running firewalls, the firewall may be blocking the traffic. Consult your OS/firewall documentation for details on allowing multicast traffic.

Multiple NICs : If your machines have multiple network interfaces you may try specifying an explicit interface via the -local test parameter. For example, if Server A has two interfaces with IP addresses 195.0.0.1 and 195.0.100.1, including -local 195.0.0.1 on the test command line would ensure that the multicast packets used the first interface.  
                              
Note :If multicast is not functioning properly, you will need to consult with your network administrator or sysadmin to determine the cause and to correct the situation. Also, sometimes the default value of 4 for "ttl" is not sufficient, so increase the value of ttl gradually by 5 and run the multicast test between both machines as
            
"java com.tangosol.net.MulticastTest -group 224.3.1.1:31341 -ttl 20"

2) . By default, BE uses "224.3.3.1" and "33389" as Multicast Address & Port respectively which are defaults provided in
"tangosol-coherence.xml" and packaged in "coherence.jar". If you do not want to use the default Multicast Address and Port as provided in "coherence.jar", the following two properties can be added in the BE .tra file to override them -      

                java.property.tangosol.coherence.clusteraddress=&ltAddress Value>
                java.property.tangosol.coherence.clusterport=&ltPort Value>


For overriding the default value of of 4 for ttl, the following property needs to be added in the tra file.                

                java.property.tangosol.coherence.ttl=&ltsome integer value like 5,10,15.......>