Multicast Testing

I am trying to test my multicast environment. Has anybody used or know how to use Wsend and Wlisten. I cant seem to get it working correctly.

Hi allen,
my name is Maria and I'd like configure multicast in my network but I'm confused about addressing.
Please can you tell me how to configure multicast group?
In the attachments you can look at my network.
Thank you in advance!
P.S.
Have you used vlc?I want to use this software to test my network.

Similar Messages

Duplicate message in Multicast test

I just ran a multicast test on a cluster which has 2 managed servers.Following is the result :-
Using multicast address 237.0.0.1:7001
Will send messages under the name MyServer-1 every 2 seconds
Will print warning every 600 seconds if no messages are received
I (MyServer-1) sent message num 1
New Neighbor ƒI7BÄsr ‼weblogic.rj found on message number 1997019664
Duplicate message from ƒI7BÄsr ‼weblogic.rj: 1997019664
Received message 2 from MyServer-1
I (MyServer-1) sent message num 2
Received message 3 from MyServer-1
I (MyServer-1) sent message num 3
Received message 4 from MyServer-1
I (MyServer-1) sent message num 4
Received message 5 from MyServer-1
I (MyServer-1) sent message num 5
Received message 6 from MyServer-1
I (MyServer-1) sent message num 6
Duplicate message from ƒI7BÄsr ‼weblogic.rj: 1997019664
Duplicate message from ƒI7BÄsr ‼weblogic.rj: 1997019664
Received message 7 from MyServer-1
I (MyServer-1) sent message num 7
Received message 8 from MyServer-1
I (MyServer-1) sent message num 8
Received message 9 from MyServer-1
I (MyServer-1) sent message num 9
Received message 10 from MyServer-1
I (MyServer-1) sent message num 10
Received message 11 from MyServer-1
I (MyServer-1) sent message num 11
Duplicate message from ƒI7BÄsr ‼weblogic.rj: 1997019664
Duplicate message from ƒI7BÄsr ‼weblogic.rj: 1997019664
Can anyone tel me what the following 2 lines indicate:-
Duplicate message from ƒI7BÄsr ‼weblogic.rj: 1997019664
Duplicate message from ƒI7BÄsr ‼weblogic.rj: 1997019664

we are using weblogic 9.2 and we are seeing the same messages when we use the same multicast address configured in config.xml and with the different multiast address. Can anyone tell what is the reason for this.

Coherence Multicast test fails on rPath linux

Hi,
I am trying to run coherence on rPath Linux, when i run the multicast-test.sh it fails with the following error - "java.io.IOException: Operation not permitted".
Am I missing out on any config setting?
Configuring multicast socket...
Starting listener...
Mon Dec 14 13:47:00 UTC 2009: Sent packet 1.
2009-12-14 13:47:00.669/0.821 Oracle Coherence GE 3.5.2/463 <Error> (thread=main, member=n/a): An exception occurred while executing the MulticastTest:
2009-12-14 13:47:00.670/0.822 Oracle Coherence GE 3.5.2/463 <Error> (thread=main, member=n/a): (Wrapped) java.io.IOException: Operation not permitted
at com.tangosol.util.Base.ensureRuntimeException(Base.java:293)
at com.tangosol.util.Base.ensureRuntimeException(Base.java:269)
at com.tangosol.net.MulticastTest.run(MulticastTest.java:303)
at com.tangosol.net.MulticastTest.main(MulticastTest.java:126)
Caused by: java.io.IOException: Operation not permitted
at java.net.PlainDatagramSocketImpl.send(Native Method)
at java.net.DatagramSocket.send(Unknown Source)
at com.tangosol.net.MulticastTest.run(MulticastTest.java:295)
... 1 more
2009-12-14 13:47:00.670/0.822 Oracle Coherence GE 3.5.2/463 <Error> (thread=main, member=n/a):
Exiting MulticastTest
Thanks,
Prakash

Thanks.
I found out the issue. It because of IP Tables blocking off multicast packets.
Once I stopped IP Tables everything worked fine. Looks like I will have to modify the rules.

Software Image for c3745 for MPLS/Multicast Test Lab

Looking to find an IOS Image for a c3745 that will support the "address-family ipv4 mdt" under BGP for Multicast. Can anybody assist me here. I have tried the Software Advisor without any success.
Thanks
Derek

Derek,
Sorry, I had read 3750. It is available starting with 12.4(20)T for the 3745.
Regards

Duplicate messages in mulitcast test

We are doing a multicast test on the multicast IP=224.0.0.115 port=61101. But we are getting some duplicate messages as given in the test output.
This is done from host sjh75a01,sjh75a02,sjh75a03,sjh75a04,sjh75a05
sjh75a01 neop04 $ java utils.MulticastTest -N sjh75a01 -a 224.0.0.115 -p 61101 -s 5
***** WARNING ***** WARNING ***** WARNING *****
Do NOT use the same multicast address as a running WLS cluster.
Starting test. Hit any key to abort
Using multicast address 224.0.0.115:61101
Will send messages under the name sjh75a01 every 5 seconds
Will print warning every 600 seconds if no messages are received
I (sjh75a01) sent message num 1
Duplicate message from sjh75a01: 1
New Neighbor sjh75a02 found on message number 1
New Neighbor sjh75a03 found on message number 1
New Neighbor sjh75a04 found on message number 1
New Neighbor sjh75a05 found on message number 1
I (sjh75a01) sent message num 2
Received message 2 from sjh75a01
Duplicate message from sjh75a01: 2
Received message 2 from sjh75a02
Received message 2 from sjh75a03
Received message 2 from sjh75a04
Received message 2 from sjh75a05
we have Weblogic servers on 5 physical hosts that need to broadcast messages to each other via IP multicast (IP=224.0.0.115 port=61101). These broadcast messages are used by WebLogic servers to update their cluster membership and are hence very important.
The test results indicate that each host receives packets sent out from all other 4 hosts once, but receives the packet that it sent out twice.
For example, if host A and host B send out packets "a" and "b" respectively to the multicast IP/port, then host A receives packet "a" twice (duplicate) and packet "b" once (normal). Similarly host B receives packet "a" once (normal) and packet "b" twice (duplicate).
We wish to know if this a normal behaviour

Hi Deepak,
I can say from my personal experience that whenever we use same multicast ip address and port for the purpose of multicast utility then we will get the duplicate messages.
If that is not the case, then I can say the following are the reasons for duplicate packets and it is better if we can contact your network team to check the following :
***Duplicate multicast packets are symptoms of several things:***
1. An ethernet-level device (e.g. bridge) that doesn't understand multicast so reforwards it. This is easy to track to the right subnet using mtrace's packet statistics, but hard to track to the final device because it doesn't change the ethernet source address.
2. The design of the PIM protocol accepts multiple copies periodically; when there are multiple paths to a multi-access link the default state is that all routers on the link forward; PIM Assert messages elect a single router as the forwarder but periodically time out.
3. Forwarding loops. This is often due to a misconfigured router.
Please cross verify the same but I am agreeing partly with Jay as most of the times we consider that the multicast test is passed even if there is any duplicate messages. But reconsider the above reasons and trace it out along with your network team..
Thanks,
Sreedevi

Multicast issue with Win XP

          I am wondering if anyone else has encountered Multicast problems with Windows XP.
          I think I am, and believe these issues are preventing the servers in my clusters
          from syncing their JNDI tree bindings.
          I noticed this while configuring a JMS Server and Queues in a clustered development
          environment. It is a simple cluster of 2 servers both on a single Win XP machine,
          see post 14712 in weblogic.developer.interest.jms (http://newsgroups2.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jms&item=14712&utag=).
          I tried the MultiCast test utility (http://e-docs.bea.com/wls/docs81/admin_ref/utils.html#1199798)
          and found what I think means I have a multicast problem. Output follows:
          ------ Begin MultiCast test utility output: ------
          C:\bea\weblogic81\server\lib>java -cp weblogic.jar utils.MulticastTest -N server200
          -A 237.155.155.1 -t 15
          ***** WARNING ***** WARNING ***** WARNING *****
          Do NOT use the same multicast address as a running WLS cluster.
          Starting test. Hit any key to abort
          Using multicast address 237.155.155.1:7001
          Will send messages under the name server200 every 2 seconds
          Will print warning every 15 seconds if no messages are received
          I (server200) sent message num 1
          I (server200) sent message num 2
          I (server200) sent message num 3
          I (server200) sent message num 4
          I (server200) sent message num 5
          I (server200) sent message num 6
          I (server200) sent message num 7
          java.net.SocketTimeoutException: Receive timed out
          at java.net.PlainDatagramSocketImpl.receive(Native Method)
          at java.net.DatagramSocket.receive(Unknown Source)
          at utils.MulticastTest$Receiver.run(MulticastTest.java:304)
          I (server200) sent message num 8
          I (server200) sent message num 9
          I (server200) sent message num 10
          I (server200) sent message num 11
          ------ End MultiCast test utility output: ------
          I expected to see "Received message X from server200" messages, like I saw from
          the Win2K machines I tried.
          There is a Microsoft Knowledge Base Article - 827536, "An IP multicast may not
          be sent correctly from Windows XP or from Windows Server 2003" (http://support.microsoft.com/default.aspx?scid=kb;en-us;827536).
          The issue appears to be limited to computers with more than one network adapter
          (like I have). I am pursuing the hotfix from Microsoft, but these things take
          time.
          Anyone else having similar issues?
          Any and all help is appreciated.


          I am facing a problem and believe that its because of multicast too. The problem
          is seen on XP but not on W2000.
          The MulticastTest when executed does not show any message exchange at all. When
          a server is started I get following exception
          <BEA-000364> <Server failed during initialization. Exception:weblogic.server.ServerLifecycleException:
          Failed to listen on multicast address
          weblogic.server.ServerLifecycleException: Failed to listen on multicast address
               at weblogic.cluster.ClusterCommunicationService.initialize(ClusterCommunicationService.java:57)
               at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:922)
               at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:664)
               at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:342)
               at weblogic.Server.main(Server.java:32)
          Caused by: java.net.SocketException: error setting options
               at java.net.PlainDatagramSocketImpl.join(Native Method)
               at java.net.PlainDatagramSocketImpl.join(PlainDatagramSocketImpl.java:134)
               at java.net.MulticastSocket.joinGroup(MulticastSocket.java:274)
               at weblogic.cluster.FragmentSocket.initializeMulticastSocket(FragmentSocket.java:92)
               at weblogic.cluster.FragmentSocket.start(FragmentSocket.java:109)
               at weblogic.cluster.MulticastManager.startListening(MulticastManager.java:164)
               at weblogic.cluster.ClusterCommunicationService.initialize(ClusterCommunicationService.java:52)
               ... 4 more
          >
          Are you experiencing similar problem ?
          Parag
          "Andy Frank" <[email protected]> wrote:
          >
          >I am wondering if anyone else has encountered Multicast problems with
          >Windows XP.
          > I think I am, and believe these issues are preventing the servers in
          >my clusters
          >from syncing their JNDI tree bindings.
          >
          >
          >I noticed this while configuring a JMS Server and Queues in a clustered
          >development
          >environment. It is a simple cluster of 2 servers both on a single Win
          >XP machine,
          >see post 14712 in weblogic.developer.interest.jms (http://newsgroups2.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jms&item=14712&utag=).
          >
          >
          >I tried the MultiCast test utility (http://e-docs.bea.com/wls/docs81/admin_ref/utils.html#1199798)
          >and found what I think means I have a multicast problem. Output follows:
          >
          >
          >------ Begin MultiCast test utility output: ------
          >C:\bea\weblogic81\server\lib>java -cp weblogic.jar utils.MulticastTest
          >-N server200
          >-A 237.155.155.1 -t 15
          >***** WARNING ***** WARNING ***** WARNING *****
          >Do NOT use the same multicast address as a running WLS cluster.
          >
          >
          >Starting test. Hit any key to abort
          >
          >
          >Using multicast address 237.155.155.1:7001
          >Will send messages under the name server200 every 2 seconds
          >Will print warning every 15 seconds if no messages are received
          >
          > I (server200) sent message num 1
          > I (server200) sent message num 2
          > I (server200) sent message num 3
          > I (server200) sent message num 4
          > I (server200) sent message num 5
          > I (server200) sent message num 6
          > I (server200) sent message num 7
          >java.net.SocketTimeoutException: Receive timed out
          > at java.net.PlainDatagramSocketImpl.receive(Native Method)
          > at java.net.DatagramSocket.receive(Unknown Source)
          > at utils.MulticastTest$Receiver.run(MulticastTest.java:304)
          > I (server200) sent message num 8
          > I (server200) sent message num 9
          > I (server200) sent message num 10
          > I (server200) sent message num 11
          >------ End MultiCast test utility output: ------
          >
          >I expected to see "Received message X from server200" messages, like
          >I saw from
          >the Win2K machines I tried.
          >
          >
          >There is a Microsoft Knowledge Base Article - 827536, "An IP multicast
          >may not
          >be sent correctly from Windows XP or from Windows Server 2003" (http://support.microsoft.com/default.aspx?scid=kb;en-us;827536).
          > The issue appears to be limited to computers with more than one network
          >adapter
          >(like I have). I am pursuing the hotfix from Microsoft, but these things
          >take
          >time.
          >
          >
          >Anyone else having similar issues?
          >
          >Any and all help is appreciated.

Multicast socket receive error: java.io.InterruptedIOException: Receive timed out

Hello
          We have One Admin and 2 Mananged server on same machine.
          It is a quad server.
          With 2 NICs.
          Managed Server is giving this error.
          <Jul 22, 2002 10:55:54 AM CDT> <Error> <Cluster> <Multicast socket
          receive error
          : java.io.InterruptedIOException: Receive timed out
          java.io.InterruptedIOException: Receive timed out
          at java.net.PlainDatagramSocketImpl.receive(Native Method)
          at java.net.PlainDatagramSocketImpl.receive(PlainDatagramSocketImpl.java
          :90)
          at java.net.DatagramSocket.receive(DatagramSocket.java:404)
          at weblogic.cluster.FragmentSocket.receive(FragmentSocket.java:145)
          at weblogic.cluster.MulticastManager.execute(MulticastManager.java:298)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >
          Also on weblogic console
          Cluster - > Monitoring - > Monitor Server Participation Panel
          shows that both our managed servers are part of the cluster..
          But only Sent Frames has data.. Receive frame does not seem to be
          working.
          I tried MultiCastTest Utility in 2 different dos prompts and seems to
          be working. (both windows shows send/receive).
          Though i am not sure if it will work for a quad / 2NIC machine..
          As utility does not take IP address of the server.
          thanks


that is right.
          we fixed it.. we tried running multicast test and it failed
          so we had to fix our network settings and got multicast working.
          also due to multiple NIC card we had to set "interface" address
          which we had not done while working with single NIC machines
          in clustered mode.
          thanks
          Kumar Allamraju <[email protected]> wrote in message news:<[email protected]>...
          > I have seen this error once when the multicastddress is not properly setup.
          > Can you try a different multicastAddress and see if that makes any difference?
          >
          >
          > zevit wrote:
          >
          > > Hello
          > >
          > > We have One Admin and 2 Mananged server on same machine.
          > > It is a quad server.
          > > With 2 NICs.
          > >
          > > Managed Server is giving this error.
          > >
          > > <Jul 22, 2002 10:55:54 AM CDT> <Error> <Cluster> <Multicast socket
          > > receive error
          > > : java.io.InterruptedIOException: Receive timed out
          > > java.io.InterruptedIOException: Receive timed out
          > > at java.net.PlainDatagramSocketImpl.receive(Native Method)
          > > at java.net.PlainDatagramSocketImpl.receive(PlainDatagramSocketImpl.java
          > > :90)
          > > at java.net.DatagramSocket.receive(DatagramSocket.java:404)
          > > at weblogic.cluster.FragmentSocket.receive(FragmentSocket.java:145)
          > > at weblogic.cluster.MulticastManager.execute(MulticastManager.java:298)
          > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > > >
          > >
          > > Also on weblogic console
          > >
          > > Cluster - > Monitoring - > Monitor Server Participation Panel
          > > shows that both our managed servers are part of the cluster..
          > > But only Sent Frames has data.. Receive frame does not seem to be
          > > working.
          > >
          > > I tried MultiCastTest Utility in 2 different dos prompts and seems to
          > > be working. (both windows shows send/receive).
          > > Though i am not sure if it will work for a quad / 2NIC machine..
          > > As utility does not take IP address of the server.
          > >
          > > thanks

Multicast not working with Window2K Network Load Balancing.

I'm using W2K Network Load Balancing (WBLB) for our cluster machines (2
          boxes) to load balance between IIS (one IIS instance on each box). Each IIS
          instance is a proxy to the weblogic cluster (one app server instance on each
          box). Currently I only have a single network card configured for each box,
          so I have had to enable multicast support for the WNLB. But if I do this
          I'm unable to get multicasting working correctly for the weblogic cluster.
          When I run the multicast tester (utils.MulticastTest) one box is able to
          receive multicast messages from both boxes, but the other box is only
          receiving multicast messages from itself (but not the other box). Does
          anyone have any experience with configuring weblogic clustering on machines
          with WNLB also configured?
          Thank you.
          Marko.


Hi
NLB return traffic for UDP would come from the node IPs.
You could use NAT on your firewalls so they come from the same public IP.
Otherwise you'd be looking at something other than MS NLB.
Cheers
GF

Coherence and Multicast Issues

We are using Coherence 3.7.1 as a part of EAR application. These are deployed on WL Servers using multicast. We have observed if multicast is disabled on a node while deployment but enabled later, id does not joins the cluster, A redeployment is required after multicast is re-enabled.
Any suggestions on this will be appreciated.
Though one option option is to run the the multicast-test.cmd utility manually before deployment and view the result, is there a way to automate this process without manual intervention.
Using Unicast and WKA are not possible
Looking forward to suggestions.

Raff. wrote:
Can you try to run your application linked to the 10.1 LCCS lib on a machine that only has FlashPlayer 10.0 installed ?
Can an application which is linked to lccs for player 10.1, run on a 10.0 player?
This sounds like a problem in lccs. Could you check the difference in code in WebcamSubscriber#playStream() between 10.0 and 10.1? (I cannot do this as 10.1 is not open source.) Whatever the problem is, it's initiated from that method.

Multicast (clustering) behind a VPN

Hi all,
When I work from home over a VPN, I can't get 2 WLS 9 servers (on my laptop) to form a cluster. I get these errors in the log:
<Aug 14, 2009 4:30:02 PM CDT> <Error> <Cluster> <BEA-000170> <Server busB did no
t receive the multicast packets that were sent by itself>
<Aug 14, 2009 4:30:02 PM CDT> <Critical> <Health> <BEA-310006> <Critical Subsyst
em Cluster has failed. Setting server state to FAILED.
Reason: Unable to receive self generated multicast messages>
I've tried setting the interface address to blank, localhost, 127.0.0.1, and the VPN-assigned ip address. I've also tried increasing the ttl. I get the same results every time.
I also tried using various multicast test utilities but they don't seem to receive their own messages, either.
I know to get Oracle Coherence to cluster behind a VPN at startup I have to set a well-known address property to my IP address.
This is with WLS 9.2.3 and XP Pro. Any idea what I can do with WLS?
thanks

Have you attempted to set up a MS Loopback Adapter and binding the WLS servers to that network interface? Not sure if it'll work, just an idea.

Coherence multicast issue - nodes leaves, cannot join back

We have six nodes in a cluster. We use multicast with a TTL=1. The nodes are all part of same VLAN.
After certain period of inactivity, we see multiple nodes leaving the cluster with messages like below...
2011-11-22 18:47:52,973 ERROR [STDERR] 2011-11-22 18:47:52.972/1840.837 Oracle Coherence GE 3.5.1/461 <Error> (thread=PacketListenerN, member=2): Stopping cluster due to unhandled exception: com.tangosol.net.messaging.ConnectionException: Unable to refresh sockets: [UnicastUdpSocket{State=STATE_OPEN, address:port=10.137.2.64:8088}, MulticastUdpSocket{State=STATE_OPEN, address:port=224.3.5.7:35473, InterfaceAddress=10.137.2.64, TimeToLive=1}, TcpSocketAccepter{State=STATE_OPEN, ServerSocket=10.137.2.64:8088}]; last failed socket: MulticastUdpSocket{State=STATE_OPEN, address:port=224.3.5.7:35473, InterfaceAddress=10.137.2.64, TimeToLive=1}
     at com.tangosol.coherence.component.net.Cluster$SocketManager.refreshSockets(Cluster.CDB:91)
     at com.tangosol.coherence.component.net.Cluster$SocketManager$MulticastUdpSocket.onInterruptedIOException(Cluster.CDB:9)
     at com.tangosol.coherence.component.net.socket.UdpSocket.receive(UdpSocket.CDB:33)
     at com.tangosol.coherence.component.net.UdpPacket.receive(UdpPacket.CDB:4)
     at com.tangosol.coherence.component.util.daemon.queueProcessor.packetProcessor.PacketListener.onNotify(PacketListener.CDB:19)
     at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
     at java.lang.Thread.run(Thread.java:662)
Caused by: java.net.SocketTimeoutException: Receive timed out
     at java.net.PlainDatagramSocketImpl.receive0(Native Method)
     at java.net.PlainDatagramSocketImpl.receive(PlainDatagramSocketImpl.java:145)
     at java.net.DatagramSocket.receive(DatagramSocket.java:725)
     at com.tangosol.coherence.component.net.socket.UdpSocket.receive(UdpSocket.CDB:20)
     at com.tangosol.coherence.component.net.UdpPacket.receive(UdpPacket.CDB:4)
     at com.tangosol.coherence.component.util.daemon.queueProcessor.packetProcessor.PacketListener.onNotify(PacketListener.CDB:19)
     at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
     at java.lang.Thread.run(Thread.java:662)
2011-11-22 18:47:52,973 ERROR [STDERR] 2011-11-22 18:47:52.973/1840.838 Oracle Coherence GE 3.5.1/461 <D5> (thread=Cluster, member=2): Service Cluster left the cluster
2011-11-22 18:47:53,093 ERROR [STDERR] 2011-11-22 18:47:53.090/1840.955 Oracle Coherence GE 3.5.1/461 <D5> (thread=DistributedCache, member=2): Service DistributedCache left the cluster+
The exact same message appears on 4 out of 6 nodes. Other two nodes then join back and form a smaller cluster.
When the next request goes to one of the "dead" node, that node tries to join back with the original cluster and it fails with the message below. The same kind of message happens on another server as well. Thus neither can join back the original cluster or form a new one.
Questions:
*1. Why would the members leave?"*
*2. When they try to join back why do they get exceptions trying to join back to the cluster?"*
*3. What are the recommendation to ensure that the members can join back? How can we increase the retry count so that they don't give up on retrying after 3 attempts?"*
*4. Is there something to be concerned about when it says "Service DistributedCache left the cluster"? What is its meaning?*
2011-11-23 14:11:31,559 ERROR [STDERR] 2011-11-23 14:11:31.559/71659.424 Oracle Coherence GE 3.5.1/461 <D5> (thread=Cluster, member=n/a): Service Cluster joined the cluster with senior service member n/a
2011-11-23 14:11:58,045 ERROR [STDERR] 2011-11-23 14:11:58.045/71685.910 Oracle Coherence GE 3.5.1/461 <Warning> (thread=Cluster, member=n/a): This Member(Id=0, Timestamp=2011-11-23 14:11:31.499, Address=10.137.2.64:8088, MachineId=33088, Location=site:company.net,machine:host2,process:3527) has been attempting to join the cluster at address 224.3.5.7:35473 with TTL 1 for 26 seconds without success; this could indicate a mis-configured TTL value, or it may simply be the result of a busy cluster or active failover.
2011-11-23 14:11:58,047 ERROR [STDERR] 2011-11-23 14:11:58.047/71685.912 Oracle Coherence GE 3.5.1/461 <Warning> (thread=Cluster, member=n/a): Received a discovery message that indicates the presence of an existing cluster that does not respond to join requests; this is usually caused by a network layer failure:
Message "SeniorMemberHeartbeat"
FromMember=Member(Id=1, Timestamp=2011-11-22 18:15:41.108, Address=10.137.2.63:8088, MachineId=33087, Location=site:ie.intuit.net,machine:qypprdfisap01,process:13982, Role=JavaLangThread)
FromMessageId=0
Internal=false
MessagePartCount=1
PendingCount=0
MessageType=17
ToPollId=0
Poll=null
Packets
[000]=Broadcast{PacketType=0x0DDF00D2, ToId=0, FromId=1, Direction=Incoming, ReceivedMillis=14:11:58.45, MessageType=17, MessagePartCount=1, MessagePartIndex=0, Body=0x0000000133CE3505340A89023F00000000000000000000000040001F980000813F0001050104040E636C75737465723A3078433541420D69652E696E747569742E6E6574400D71797070726466697361703031053133393832400E4A6176614C616E67546872656164000000000133D27C381B010000000500, Body.length=121}
Service=ClusterService{Name=Cluster, State=(SERVICE_STARTED, STATE_ANNOUNCE), Id=0, Version=3.5}
ToMemberSet=null
NotifySent=false
LastRecvTimestamp=Wed Nov 23 14:11:56 PST 2011
MemberSet=MemberSet(Size=2, BitSetCount=1, ids=[1, 3])
2011-11-23 13:24:03,630 ERROR [STDERR] 2011-11-23 13:24:03.628/68794.632 Oracle Coherence GE 3.5.1/461 <D5> (thread=Cluster, member=n/a): Service Cluster left the cluster
2011-11-23 13:24:03,632 ERROR [STDERR] 2011-11-23 13:24:03.632/68794.636 Oracle Coherence GE 3.5.1/461 <Error> (thread=ajp-0.0.0.0-8009-1, member=n/a): Error while starting cluster: com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
MemberSet=ServiceMemberSet(
OldestMember=n/a
ActualMemberSet=MemberSet(Size=0, BitSetCount=0
MemberId/ServiceVersion/ServiceJoined/ServiceLeaving
)

Please do a test with %Coherence_Home%\bin\multicast-test.cmd to check that multicast is OK....
and the do a test with %Coherence_Home%\bin\datagram-test.cmd to check your network performance....
Look at the documentation it is well documented...

Multicast Problems

I have four machines, split over a Wan, two at each location. The routers and switches have been configured appropriately, so multicast should work between the sites. I when I run the multicast test utility the machines can see the machines in the same location but do not see the machines in the remote location. However if I ping the multicast group from any of the machines I get a response from all four servers. This is running on Linux
Machines have the following ips
Machine 1 Site 1: 172.20.50.93
Machine 1 Site 2: 172.20.150.151
Machine 1 Site 2: 172.20.150.152
If I have the multicast test running on three servers here are the results: -
Ping from machine 1 on site1( ping 230.30.30.30 -t 64 ):
64 bytes from 172.20.150.151: icmp_seq=587 ttl=61 time=2.92 ms (DUP!)
64 bytes from 172.20.150.152: icmp_seq=587 ttl=61 time=2.93 ms (DUP!)
64 bytes from 172.20.50.93: icmp_seq=588 ttl=64 time=0.015 ms
64 bytes from 172.20.150.151: icmp_seq=588 ttl=61 time=2.92 ms (DUP!)
64 bytes from 172.20.150.152: icmp_seq=588 ttl=61 time=2.93 ms (DUP!)
64 bytes from 172.20.50.93: icmp_seq=589 ttl=64 time=0.015 ms
64 bytes from 172.20.150.151: icmp_seq=589 ttl=61 time=2.93 ms (DUP!)
64 bytes from 172.20.150.152: icmp_seq=589 ttl=61 time=2.93 ms (DUP!)
Multicast test from machine1 Site1:
Thu Apr 13 05:24:36 EDT 2006: Sent packet 5.
Thu Apr 13 05:24:36 EDT 2006: Received packet 5 from self.
Thu Apr 13 05:24:37 EDT 2006: Sent packet 6.
Thu Apr 13 05:24:37 EDT 2006: Received packet 6 from self
Multicast test from machine1 Site2:
Thu Apr 13 05:24:37 EDT 2006: Sent packet 10.
Thu Apr 13 05:24:37 EDT 2006: Received packet 10 from self.
Thu Apr 13 05:24:37 EDT 2006: Received packet 8 from ip=172.20.150.152, group=224.30.30.30, port=4000, ttl=64.
Thu Apr 13 05:24:38 EDT 2006: Sent packet 11.
Thu Apr 13 05:24:38 EDT 2006: Received packet 11 from self.
Thu Apr 13 05:24:38 EDT 2006: Received packet 9 from ip=172.20.150.152, group=224.30.30.30, port=4000, ttl=64.
Multicast test from machine1 Site2:
Thu Apr 13 05:24:36 EDT 2006: Sent packet 7.
Thu Apr 13 05:24:36 EDT 2006: Received packet 7 from self.
Thu Apr 13 05:24:37 EDT 2006: Received packet 10 from ip=172.20.150.151, group=224.30.30.30, port=4000, ttl=64.
Thu Apr 13 05:24:37 EDT 2006: Sent packet 8.
Thu Apr 13 05:24:37 EDT 2006: Received packet 8 from self.
Thu Apr 13 05:24:38 EDT 2006: Received packet 11 from ip=172.20.150.151, group=224.30.30.30, port=4000, ttl=64.
The ping seems to suggest that the machines can communicate, can you shed any light on this.
Thanks
Oliver

Hi,
The OS is Red Hat Enterprise Linux ES release 4 (Nahant Update 3)
The Coherence version is 3.0
Machine 1 Site 1:
java -jar multicast-test.jar 172.20.50.92 224.30.30.30 4000 64 1
Machine 2 Site 1
java -jar multicast-test.jar 172.20.50.93 224.30.30.30 4000 64 1
Machine 1 Site 2
java -jar multicast-test.jar 172.20.150.151 224.30.30.30 4000 64 1
Machine 2 Site 2
java -jar multicast-test.jar 172.20.150.152 224.30.30.30 4000 64 1
If I run the above on all four machines, both machines at Site 1 can see each other, both machines at Site 2 can see each other, the ping gets a response from all four. But machines from Site 1 and Site 2 dont see each other.
Thanks
Oliver

What is the default multicast TTL?

been using the US Navy's MGEN multicast test utility for a while. Recently upgraded to Lion. The help doc states:
If no ttl option is used, MGEN will behave according to the operating system's default behavior.
I did a trace an the TTL was 3. Are you kidding me? Why would a mcast TTL default to 3?
absurd...

You can check the specs of ALL iBook models (G3 + G4) at everymac.com
http://www.everymac.com/systems/apple/ibook/index-ibook.html
If your iBook has a processor less than 867MHz it won't be able to run
Mac OS X 10.5 Leopard, though methods exist to allow it unofficially.
Old first model colors iBook G3 (not white dualUSB) have other limits.
A reference app for Apple product specifications, download http://mactracker.ca
Hopefully you can match your questions with the various databases online.
Good luck & happy computing!

Binding Multicast to a NIC

          Our WLS 4.51 servers (two in a cluster) each have a pair of NICs so that we can dedicate
          a back-end subnet to the multicasts the two servers need to communicate with one
          another.
          Do we need to somehow bind the multicasting to the NICs in question via the properties
          file or a -D option? I'm thinking no, since the other NICs are on a subnet that doesn't
          allow multicasting and I'm able to successfully run the multicasting test -- the
          two boxes talk just fine. However, I'm worried that leaving the servers to find the
          second subnet on their own is slowing them down and perhaps contributing to the real
          problem we're seeing -- Timed Out Server errors.
          John Guilfoyle
          Saillant Consulting Group


          Yes, you can (actually you MUST) bind the multicast traffic to one
          NIC.
          The per-server property is:
          weblogic.cluster.interfaceAddress=<IP of NIC to bind to >
          The problem is that you will need a special patch from BEA to do
          this.
          I'm sure they will put it in the next service pack, but until then,
          you need the patch.
          "John Guilfoyle" <[email protected]> wrote:
          >
          >Our WLS 4.51 servers (two in a cluster) each have a pair
          >of NICs so that we can dedicate
          >a back-end subnet to the multicasts the two servers need
          >to communicate with one
          >another.
          >
          >Do we need to somehow bind the multicasting to the NICs
          >in question via the properties
          >file or a -D option? I'm thinking no, since the other
          >NICs are on a subnet that doesn't
          >allow multicasting and I'm able to successfully run the
          >multicasting test -- the
          >two boxes talk just fine. However, I'm worried that leaving
          >the servers to find the
          >second subnet on their own is slowing them down and perhaps
          >contributing to the real
          >problem we're seeing -- Timed Out Server errors.
          >
          >John Guilfoyle
          >Saillant Consulting Group

Managed server not able to join the cluster

Hi
I have two storage node enabled coherence servers on two different machines.These two are able to form the cluster without any problem. I also have two Managed servers. When I start one, will join the cluster without any issue but when I start the fourth one which does not join the cluster. Only one Managed server joins the cluster. I am getting the following error.
2011-12-22 15:39:26.940/356.798 Oracle Coherence GE 3.6.0.4 <Info> (thread=[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)', member=n/a): Loaded cache configuration from "file:/u02/oracle/admin/atddomain/atdcluster/ATD/config/atd-client-cache-config.xml"
2011-12-22 15:39:26.943/356.801 Oracle Coherence GE 3.6.0.4 <D4> (thread=[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)', member=n/a): TCMP bound to /172.23.34.91:8190 using SystemSocketProvider
2011-12-22 15:39:57.909/387.767 Oracle Coherence GE 3.6.0.4 <Warning> (thread=Cluster, member=n/a): This Member(Id=0, Timestamp=2011-12-22 15:39:26.944, Address=172.23.34.91:8190, MachineId=39242, Location=site:dev.icd,machine:appsoad2-web2,process:24613, Role=WeblogicServer) has been attempting to join the cluster at address 231.1.1.50:7777 with TTL 4 for 30 seconds without success; this could indicate a mis-configured TTL value, or it may simply be the result of a busy cluster or active failover.
2011-12-22 15:39:57.909/387.767 Oracle Coherence GE 3.6.0.4 <Warning> (thread=Cluster, member=n/a): Received a discovery message that indicates the presence of an existing cluster:
Message "NewMemberAnnounceWait"
FromMember=Member(Id=2, Timestamp=2011-12-22 15:22:56.607, Address=172.23.34.74:8090, MachineId=39242, Location=site:dev.icd,machine:appsoad4,process:23937,member:CoherenceServer2, Role=WeblogicWeblogicCacheServer)
FromMessageId=0
Internal=false
MessagePartCount=1
PendingCount=0
MessageType=9
ToPollId=0
Poll=null
Packets
[000]=Broadcast{PacketType=0x0DDF00D2, ToId=0, FromId=2, Direction=Incoming, ReceivedMillis=15:39:57.909, MessageType=9, ServiceId=0, MessagePartCount=1, MessagePartIndex=0, Body=0}
Service=ClusterService{Name=Cluster, State=(SERVICE_STARTED, STATE_ANNOUNCE), Id=0, Version=3.6}
ToMemberSet=null
NotifySent=false
ToMember=Member(Id=0, Timestamp=2011-12-22 15:39:26.944, Address=172.23.34.91:8190, MachineId=39242, Location=site:dev.icd,machine:appsoad2-web2,process:24613, Role=WeblogicServer)
SeniorMember=Member(Id=1, Timestamp=2011-12-22 15:22:53.032, Address=172.23.34.73:8090, MachineId=39241, Location=site:dev.icd,machine:appsoad3,process:19339,member:CoherenceServer1, Role=WeblogicWeblogicCacheServer)
2011-12-22 15:40:02.915/392.773 Oracle Coherence GE 3.6.0.4 <Warning> (thread=Cluster, member=n/a): Received a discovery message that indicates the presence of an existing cluster:
Message "NewMemberAnnounceWait"
FromMember=Member(Id=2, Timestamp=2011-12-22 15:22:56.607, Address=172.23.34.74:8090, MachineId=39242, Location=site:dev.icd,machine:appsoad4,process:23937,member:CoherenceServer2, Role=WeblogicWeblogicCacheServer)
FromMessageId=0
Internal=false
MessagePartCount=1
PendingCount=0
MessageType=9
ToPollId=0
Poll=null
Packets
{

Hi,
By default Coherence uses a multicast protocol to discover other nodes when forming a cluster. Since you are having difficulties in establishing a cluster via multicast, Can you please perform a multicast test and see if multicast is configured properly.
http://wiki.tangosol.com/display/COH32UG/Multicast+Test
Hope you are using same configuration files across the cluster members and all members of the cluster must specify the same cluster name in order to be allowed to join the cluster.
<cluster-name system-property="tangosol.coherence.cluster";>xxx</cluster-name>
I would suggest, try using the unicast-listener with the well-known-addresses instead of muticast-listener.
http://wiki.tangosol.com/display/COH32UG/well-known-addresses
Add similar entries like below in your tangosol override xml..
<well-known-addresses>
<socket-address id="1">
<address> 172.23.34.91<;/address>
<port>8190</port>
</socket-address>
<socket-address id="2">
<address> 172.23.34.74<;/address>
<port> 8090</port>
</socket-address>
</well-known-addresses>
This list is used by all other nodes to find their way into the cluster without the use of multicast, thus at least one well known node must be running for other nodes to be able to join.
Hope this helps!!
Thanks,
Ashok.
<div id="isChromeWebToolbarDiv" style="display:none"></div>

Multicast Testing

Similar Messages

Maybe you are looking for