Airserver multicast mDNS problem

I have WLC 2504 running 7.4.100.0 with a single 1242AG AP
single wireless SSID on the WLC
an Apple AIRSERVER and an IPAD which should be able to do mirroring to show ipad screen on the pc
they have IPs in same subnet and have base connectivity
it just wont work! the ipad never sees the airplay server option come up
BUT
if i move these 2 systems to a cisco autonomous AP. or another commodity wireless LAN and have the 2 systems (pc/ipad) in same subnet it works
if i have the pc on wired and the ipad (wireless obviously) this work on the autonomous or commodity AP fine
so there is something "different" about using the WLC/LWAP right?
i have tried with and without the various multicast options enabled etc
please can anyone advise or help?
many thanks
dave

thank you both for helping me and for the pointers.
I have a config (attached)
I have this update to the case:-
laptop and iphone on same wireless LAN (interface3) wireless LANcalled clients34
With the command
config mdns snooping DISable
i can see the Airserver from the iPAD and it works (WITHIN) the wireless WLAN i.e. both on same WLAN and IP subnet
if i issue
config mdns snooping ENable
the
Airserver disappears and wont work
it comes back as soon as i disable the mdns snooping
this is consistently reproducible
any ideas welcomed
it never works between WLANs (so far!)
dave
here is the config
config location expiry tags 5
config interface address management 10.99.98.40 255.255.255.128 10.99.98.1
config interface dhcp management primary 10.99.98.3
config interface port management 1
config interface vlan management 10
config interface address virtual 1.1.1.1
config interface address dynamic-interface clients33 10.10.33.6 255.255.255.0 10.10.33.1
config interface create clients33 33
config interface dhcp dynamic-interface clients33 primary 10.99.98.3
config interface port clients33 2
config interface vlan clients33 33
config interface address dynamic-interface clients34 10.10.34.6 255.255.255.0 10.10.34.1
config interface create clients34 34
config interface dhcp dynamic-interface clients34 primary 10.99.98.3
config interface port clients34 2
config interface vlan clients34 34
config 802.11b 11gsupport enable
config 802.11b cac voice sip bandwidth 64 sample-interval 20
config 802.11b cac voice sip codec g711 sample-interval 20
config 802.11b cleanair alarm device enable 802.11-nonstd
config 802.11b cleanair alarm device enable jammer
config 802.11b cleanair alarm device enable 802.11-inv
config sysname Apple
config logging traceinfo disable debugging
config logging syslog level debugging
config logging syslog level 7
config logging syslog host 10.99.98.36
config database size 2048
config country US
config advanced probe limit 2 500
config advanced probe-limit 2 500
config advanced 802.11a channel add 36
config advanced 802.11a channel add 40
config advanced 802.11a channel add 44
config advanced 802.11a channel add 48
config advanced 802.11a channel add 52
config advanced 802.11a channel add 56
config advanced 802.11a channel add 60
config advanced 802.11a channel add 64
config advanced 802.11a channel add 149
config advanced 802.11a channel add 153
config advanced 802.11a channel add 157
config advanced 802.11a channel add 161
config advanced 802.11b channel add 1
config advanced 802.11b channel add 6
config advanced 802.11b channel add 11
config mdns service query enable AFP
config mdns service create AFP _afpovertcp._tcp.local. query enable
config mdns service query enable AirPrint
config mdns service create AirPrint _ipp._tcp.local. query enable
config mdns service query enable AirTunes
config mdns service create AirTunes _raop._tcp.local. query enable
config mdns service query enable AppleRemoteDesktop
config mdns service create AppleRemoteDesktop _net-assistant._udp.local. query enable
config mdns service query enable AppleTV
config mdns service create AppleTV _airplay._tcp.local. query enable
config mdns service query enable HP_Photosmart_Printer_1
config mdns service create HP_Photosmart_Printer_1 _universal._sub._ipp._tcp.local. query enable
config mdns service query enable HP_Photosmart_Printer_2
config mdns service create HP_Photosmart_Printer_2 _cups._sub._ipp._tcp.local. query enable
config mdns service query enable Printer
config mdns service create Printer _printer._tcp.local. query enable
config mdns profile service add default-mdns-profile AirPrint
config mdns profile service add default-mdns-profile AppleTV
config mdns profile service add default-mdns-profile HP_Photosmart_Printer_1
config mdns profile service add default-mdns-profile HP_Photosmart_Printer_2
config mdns profile service add default-mdns-profile Printer
config mdns profile create default-mdns-profile
config mdns snooping enable
config mobility group domain MOBGROUP
config network rf-network-name RFGROUP
config network telnet enable
config network broadcast enable
config network multicast igmp snooping enable
config network multicast l2mcast disable service-port
config network multicast l2mcast disable virtual
config network multicast mld snooping enable
config network multicast global enable
config dhcp address-pool scope33 10.10.33.2 10.10.33.254
config dhcp default-router scope33 10.10.33.1
config dhcp create-scope scope33
config dhcp network scope33 10.10.33.0 255.255.255.0
config dhcp address-pool "scope 34" 10.10.34.2 10.10.34.254
config dhcp default-router "scope 34" 10.10.34.1
config dhcp create-scope "scope 34"
config dhcp dns-servers "scope 34" 8.8.8.8
config dhcp network "scope 34" 10.10.34.0 255.255.255.0
config dhcp lease scope33 86400
config dhcp enable scope33
config dhcp lease "scope 34" 86400
config license boot base
config license agent max-sessions 9
config 802.11a cac voice sip bandwidth 64 sample-interval 20
config 802.11a cac voice sip codec g711 sample-interval 20
config 802.11a cleanair alarm device enable 802.11-nonstd
config 802.11a cleanair alarm device enable jammer
config 802.11a cleanair alarm device enable 802.11-inv
config nmsp notification interval rssi rfid 2
config certificate generate webauth
config wlan mfp client enable 1
config wlan mfp client enable 3
config wlan mfp client enable 4
config wlan dhcp_server 1 10.99.98.3 required
config wlan security ft over-the-ds disable 1
config wlan security wpa wpa1 ciphers aes enable 1
config wlan security wpa wpa1 ciphers tkip enable 1
config wlan security wpa wpa1 enable 1
config wlan security wpa wpa2 ciphers aes disable 1
config wlan security wpa wpa2 disable 1
config wlan security wpa akm psk set-key hex encrypt 1 a1f6e0bbf14d724dc3f66873d6f810a6 786fcab479dd2b3ab7fe1e79eb569f3bcd8bec22 48 db307698ce2f6146a19f3b40cb7a52b39b8062c5d6f8f0f37d60dc98cde78d6a1e8aea0014292f6192cd1a06a447fccd000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 1
config wlan security wpa akm psk enable 1
config wlan security wpa akm 802.1x disable 1
config wlan security wpa enable 1
config wlan security web-auth server-precedence 1 local radius ldap
config wlan security wapi akm psk set-key hex encrypt 1 a1f6e0bbf14d724dc3f66873d6f810a6 786fcab479dd2b3ab7fe1e79eb569f3bcd8bec22 48 db307698ce2f6146a19f3b40cb7a52b39b8062c5d6f8f0f37d60dc98cde78d6a1e8aea0014292f6192cd1a06a447fccd000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 1
config wlan dhcp_server 3 10.99.98.3 required
config wlan security ft over-the-ds disable 3
config wlan security wpa wpa1 ciphers aes enable 3
config wlan security wpa wpa1 enable 3
config wlan security wpa wpa2 ciphers aes disable 3
config wlan security wpa wpa2 disable 3
config wlan security wpa akm psk set-key hex encrypt 1 42a623f34bd4ac9f6c4d8415be540e52 aa8f5add9351816443d374a3fa1cd76ee34ec325 48 83269c2ab1bfffb0717cf80763bf2be8e30af9de5d784f132deef8aba1ef463d37eda9fcca7b3edac4f16806799bddb0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 3
config wlan security wpa akm psk enable 3
config wlan security wpa akm 802.1x disable 3
config wlan security wpa enable 3
config wlan security web-auth server-precedence 3 local radius ldap
config wlan security wapi akm psk set-key hex encrypt 1 42a623f34bd4ac9f6c4d8415be540e52 aa8f5add9351816443d374a3fa1cd76ee34ec325 48 83269c2ab1bfffb0717cf80763bf2be8e30af9de5d784f132deef8aba1ef463d37eda9fcca7b3edac4f16806799bddb0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 3
config wlan dhcp_server 4 10.99.98.3 required
config wlan security ft over-the-ds disable 4
config wlan security wpa wpa1 ciphers aes enable 4
config wlan security wpa wpa1 enable 4
config wlan security wpa wpa2 ciphers aes disable 4
config wlan security wpa wpa2 disable 4
config wlan security wpa akm psk set-key hex encrypt 1 5032332e8e93f8a77f2d0e2f97d411e4 37dee84d8d542d677ead99c9a06b559c3c6c39e7 48 d5576ca89f5c5201557c2a30274ac2034f0881e1502f22d0fb59b2ea05c338c9e09c57844efaa2d20967d8931c7b795c000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 4
config wlan security wpa akm psk enable 4
config wlan security wpa akm 802.1x disable 4
config wlan security wpa enable 4
config wlan security web-auth server-precedence 4 local radius ldap
config wlan security wapi akm psk set-key hex encrypt 1 5032332e8e93f8a77f2d0e2f97d411e4 37dee84d8d542d677ead99c9a06b559c3c6c39e7 48 d5576ca89f5c5201557c2a30274ac2034f0881e1502f22d0fb59b2ea05c338c9e09c57844efaa2d20967d8931c7b795c000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 4
config wlan nasid Cisco_88:af:84 1
config wlan broadcast-ssid enable 1
config wlan interface 1 management
config wlan nasid Cisco_88:af:84 3
config wlan broadcast-ssid enable 3
config wlan interface 3 clients34
config wlan nasid Cisco_88:af:84 4
config wlan broadcast-ssid enable 4
config wlan interface 4 clients33
config wlan create 1 wall wall
config wlan session-timeout 1 1800
config wlan create 3 clients34 clients34
config wlan session-timeout 3 1800
config wlan create 4 clients33 clients33
config wlan session-timeout 4 1800
config wlan exclusionlist 1 60
config wlan exclusionlist 3 60
config wlan exclusionlist 4 60
config wlan wmm allow 1
config wlan wmm allow 3
config wlan mdns disable 3
config wlan wmm allow 4
config wlan enable 1
config wlan enable 3
config wlan enable 4
config ap packet-dump truncate 0
config ap packet-dump buffer-size 2048
config ap packet-dump capture-time 10
config mgmtuser add encrypt admin 1 321719832e36efcfeefd2273c587a40e 5b6894ae997a61fda287052deb92ad880db51682 16 87acec2a7c4ebbed6eee748deb8b111c0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 read-write
config mgmtuser add encrypt l8admin 1 f2fbd280a591024db06b5e26e3aea6f0 0a6c6ee6cd7de16f828232164d3edeefdce05f4a 16 ba42eb8ce58babcf06c6e402e96353d60000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 read-write
config rfid timeout 1200
config rfid status enable
config rfid mobility pango disable
transfer upload path /
transfer upload datatype config
transfer upload serverip 172.29.254.1
transfer upload filename Daves_WLC.txt
transfer download path /
transfer download serverip 172.29.254.1
transfer download filename Daves_WLC.txt

Similar Messages

Airport multicast performance problems in u-verse IPTV bridge.

I have a bunch of airport hardware, two n expresses, a draft n extreme, and a 5th generation extreme. I've recently moved to a new house and have AT&T's u-verse multicast IPTV installed. I want to put my TV somewhere without wiring and was going to just do it using a dedicated 802.11n bridge formed from either the two expresses, or the draft n extreme (at the multicast source side) and an express as a receiver.
This seems to work from a functionality perspective, I get the multicast stream into the AT&T set-top box and can watch all of the channels for extended periods of time. The problem that I run into is that I have performance problems that result in the video stuttering, pixelating, and freezing for seconds to minutes at a time. I don't understand why this is the case. The HD stream is less than 9Mbps which should be easily handled by a 5Ghz, n-only link. The source and destination expresses are within 5 feet of each other with clear line-of-sight.
Does anyone have any experience with multicast streaming on aiport hardware? Is there some limitation in the airport implementation where multicast (UDP) packets trigger some sort of slowpath packet processing, so that packets are being dropped? Is there some reporting feature within airport utility that where I can look for diagnostics related to dropped or (extremely) delayed packets? Is there something about AT&T's use of multicast IPTV that is just incompatible with airport hardware?
Note that the u-verse gateway handles all of the IGMP in this situation, and that nothing else is on the network. Well, the 5th gen router is on the network and everything else I own is behind it on a different wifi network. The gateway is smart enough to filter out the multicast traffic so that the router doesn't see it.

Found a solution. Switching from Apple's built-in "create a wireless network" and "join a wireless network+allow ethernet clients" to a WDS network with a main and a remote solves all of the problems. It's not a great option because the WDS network forces me to select a fixed, 2.4Ghz channel, but the IPTV stream is only 8-ish Mbps which seems to be doable, even with all of the wireless networks floating around my house. I guess that it could be a bigger problem during peak wifi usage around here, but we'll cross that bridge when it happens.

Multicast address problems

In the start up scripts for my cluster nodes, I set
 weblogic.system.multicastAddress=224.1.1.100, the address setup by my IT
 group.
 When I start the cluster node, I see the following lines in the log:
 Mon May 15 10:16:05 PDT 2000: <System Props>
 weblogic.system.multicastAddress = 224.1.1.100
 . <other stuff>
 Mon May 15 10:16:06 PDT 2000: <WebLogicServer> Using default cluster
 multicast address 237.0.0.1
 Mon May 15 10:16:07 PDT 2000: <WebLogicServer>
 =========================================================
 Mon May 15 10:16:07 PDT 2000: <WebLogicServer> = Joined cluster
 cluster_1 at address 237.0.0.1
 Mon May 15 10:16:07 PDT 2000: <WebLogicServer>
 =========================================================
 Why is weblogic joining the cluster at address 237.0.0.1 when I
 specified 224.1.1.100?
 In terms of the resulting behavior, jsp page requests to the proxy
 server are passed to the single cluster node and a page is generated
 without error. As soon as I add another cluster node to the cluster,
 requests that form a new session never send a response. I suspect that
 the cluster nodes are having trouble replicating the session.
 Any help?
 - Kevin


Thanks, this causes the nodes to join at the desired address.
 I am still seeing, however, that the jsp pages I want work file when
 there is one node in the cluster but hang forever when there are more
 than one nodes. The MulticastTest utility runs successfully. Can you
 suggest any other debugging options?
 - Kevin
 Prasad Peddada wrote:
 >
 > The property is weblogic.cluster.multicastAddress.
 >
 > - Prasad
 >
 > Andrew Park wrote:
 >
 > > i had a similar problem, but it was all caused by a typo in my java command
 > > line, where i set the multicast address. please double check...
 > >
 > > there is also the utils.MulticastTest utility. please refer to
 > > http://www.weblogic.com/docs51/techstart/utils.html
 > >
 > > andrew
 > >
 > > Kevin McEntee wrote in message <[email protected]>...
 > > >In the start up scripts for my cluster nodes, I set
 > > >weblogic.system.multicastAddress=224.1.1.100, the address setup by my IT
 > > >group.
 > > >
 > > >When I start the cluster node, I see the following lines in the log:
 > > >
 > > >Mon May 15 10:16:05 PDT 2000: <System Props>
 > > >weblogic.system.multicastAddress = 224.1.1.100
 > > >.
 > > >. <other stuff>
 > > >.
 > > >Mon May 15 10:16:06 PDT 2000: <WebLogicServer> Using default cluster
 > > >multicast address 237.0.0.1
 > > >Mon May 15 10:16:07 PDT 2000: <WebLogicServer>
 > > >=========================================================
 > > >Mon May 15 10:16:07 PDT 2000: <WebLogicServer> = Joined cluster
 > > >cluster_1 at address 237.0.0.1
 > > >Mon May 15 10:16:07 PDT 2000: <WebLogicServer>
 > > >=========================================================
 > > >
 > > >Why is weblogic joining the cluster at address 237.0.0.1 when I
 > > >specified 224.1.1.100?
 > > >
 > > >In terms of the resulting behavior, jsp page requests to the proxy
 > > >server are passed to the single cluster node and a page is generated
 > > >without error. As soon as I add another cluster node to the cluster,
 > > >requests that form a new session never send a response. I suspect that
 > > >the cluster nodes are having trouble replicating the session.
 > > >
 > > >Any help?
 > > >
 > > >- Kevin

EA2700 Bonjour / Multicast DNS problem

I've just updated from a Linksys E2500 to an EA2700. The new software features are great, however multicast DNS (aka zeroconf / bonjour) service discovery is not working between wired and wireless connections. (Wireless to wireless is fine, just not to wired).
The last time I saw this problem was a crappy Dlink router about 10 years ago, and I have never seen it on a Linksys produce before now (3 previous modems/routers).
I have no issues connecting to the internet, or connect to devices by their IP addresses. The problem is the service discovery, which is used for things such as Airplay video mirroring, Time Machine backups (and file sharing), iTunes music sharing and more.
Has anyone else has any issues with bonjour service discovery from wired to wireless connections on the EA2700? Or, even better, found a solution?

Hi mattconnolly ,
Most of these Linksys Routers use DLNA/UPnP for network discovery. Zeroconf creates a local domain, so devices are discoverable through names like my router.local or canon printer. local instead of its local IP address. This has been implemented on new Linksys Smart Wifi line but only for accessing it's setup page (myrouter. local) - and there were times that it breaks.
You can try to turn off/on your router, but it doesn't really fix/resolves it. You can try also to update your device's firmware. The firmware latest release update is dated 11/19/2012 (1.1.39 Build 145204) and based on the release notes, there's a Fix for Multicast traffic issue on it's release version 1.0.14 (Build 129982). Other than this, you might want to check on a much more flexible operator - WRT1900AC.
Good luck!

WES7 UDP Multicast Open problem

Hi
I am using LabVIEW 2012 SP1 programming a TPC-2206 touch-panel computer running Windows Embedded Standard 7.
I have a fairly simple program which uses the LabVIEW "UDP Multicast Open" VI to open a Read-Only multicast port, then reads data continously from it using the "UDP Read" VI.
The routine works by calling the "UDP Multicast Open" VI and if successful, then entering a continous While-loop which reads from the opened port via the opened Connection-ID refnum. If unsuccessful at opening, the routine sits there waiting for the Open to succeed, displaying a message to the user that the network is not plugged in (or similar).
My problem is that if I open the port without a network connection, the open operation succeeds (which is great as its a multicast open and that seems like the right thing it should do), but subsequently when I plug in the network with good data being sent on it, I do not receive anything?! I would have expected data to be received if the port succeeded in opening, no matter what the initial condition of the connection.
When I tried this on Windows XP, I got a open failure which let me know the network was not plugged in. I subsequently programmed it to put up the flashing message and waited for a good connection such that "UDP Multicast Open" then succeeded. Subsequent reception was then good.
Is this a known difference between WES7 and WinXP and LabVIEW "UDP Multicast Open"/"UDP Read", or am I missing something?
Thanks for any help you can give.

Thanks for the reply. I have also checked that example. Please note that in the example it doesn't have an input for the net address, which i assume labview 2011 will use 0.
I have also just received a reply from NI and confirmed it's a known bug in 2011. i will post it below.
I hope this finds you doing well. I am glad to hear that you are starting to upgrade to 2011 and I apologize for the issues you are seeing. I suspect you are using this on one of our Real-Time targets if so the good news is that this behavior has been documented in the form of a CAR (actually a
few): Broadcasts and the UDP Open VI have an INCONSISTANT behavior depending on the OS. Pharlap/Windows receive broadcasts when the "net address" terminal is wired while vxWorks/Linux don't. These CARs are scheduled as major incoviencience and will be fixed in a future version of LabVIEW as of now the work around is to simple not wire the net address field.
The CAR numbers incase you would like to see when they are fixed are:
257627, 233344,235444, 283205
LabVIEW 2011 newbie >.<
Certified LabVIEW Developer

Multicasting data problem

Hi.I am trying to multicast a long number over three clients,but when I check the number I receive, is sometimes a combination of two numbers that clients sent.For example,client 1 sends 12345(which I can read from other two clients) then client 2 sends 234567(which I can read also)after that client 3 sends 789. When I check the number received by client 1 and 2, I see that the number is 789567(combination of numbers send by client 2 and 3).I am clearing the byte arrays in datagrampacket after I send or receive.I still could not figure out how client 2 could send while client 3 is sending.Does anyone have and idea what could be the problem with that?Thanks.

This is the run method in the program:
public void run(){
 System.out.println("client " + counter);
 int fDigit=0,waiting=0;
int compareDigit[] = new int[3];
 long num=0,maxNum=0,oneturn=1;
 byte[] strn = new byte[50];
 byte[] recstrn = new byte[50];
 try {
 if(counter==1){
 strn = str.getBytes();
 message = new DatagramPacket(strn, strn.length, groupp, DEFAULT_PORT);
 client.send(message);//TTL is initially 1
 while(!done2){
 while(!done){
 DatagramPacket recv = new DatagramPacket(recstrn, recstrn.length);
 client.receive(recv);
 String s =new String(recv.getData());
 s = s.trim();//removes whitespaces
 num = Long.parseLong(s);
 fDigit = (int)(num-(num/10)*10);
 maxNum = num/10;
for(int i=0;i<3;i++){
if((compareDigit!=fDigit)&&(compareDigit[i]==0)){
compareDigit[i]=fDigit;
clientcounter++;
break;
} else if(compareDigit[i]==fDigit){
 break;
for(int i=0;i<strn.length;i++){
 strn[i]=0;
 recstrn[i]=0;
 s=" ";
 if((counter!=fDigit)||(counter==(fDigit+1))||(counter==(fDigit-2))){ //||(waiting>0)){
 waiting=0;
 System.out.println("Number read from "+counter+" leadturn "+leadturn+" newlead "+newlead+" oneturn "+oneturn);
 System.out.println("Number is "+maxNum+" from "+fDigit+" with "+times);
 if((maxNum==54321)&&(oneturn==3)){
 newlead++;
 leadturn=1;
 oneturn=1;
 str=""+maxNum+counter;
 strn = str.getBytes();
 message = new DatagramPacket(strn, strn.length,groupp,DEFAULT_PORT);
 client.send(message);
 } else if((maxNum==12345)&&(oneturn==1)){
 leadturn=2;
 oneturn++;
 System.out.println("Done "+done);
 newlead=0;
 str=""+maxNum+counter;
 strn = str.getBytes();
 message = new DatagramPacket(strn, strn.length,groupp,DEFAULT_PORT);
 client.send(message);
 } else if((maxNum==123456)&&(oneturn==2)){
 oneturn++;
 str=""+maxNum+counter;
 strn = str.getBytes();
 message = new DatagramPacket(strn, strn.length,groupp,DEFAULT_PORT);
 client.send(message);
 } else if(status!="LEADER"){
 if ((counter==(fDigit+1))||(counter==(fDigit-2))||(counter==(fDigit+2))||(counter==(fDigit-1))){
 if ((maxNum == threadID)&&(clientcounter==3)){
 System.out.println("Done");
 if(leadturn==1){
 done = true;
 status="LEADER";
 leadturn++;
 } else{
 done=true;
 status="subLEADER";
 break;
 } else if (maxNum < threadID){
 maxNum = threadID;
 str=""+maxNum+counter;
 strn = str.getBytes();
 message = new DatagramPacket(strn, strn.length,groupp,DEFAULT_PORT);
 client.send(message);
 }else{
 str=""+maxNum+counter;
 strn = str.getBytes();
 message = new DatagramPacket(strn, strn.length,groupp,DEFAULT_PORT);
 client.send(message);
 } else {
 str=""+maxNum+counter;
 strn = str.getBytes();
 message = new DatagramPacket(strn, strn.length,groupp,DEFAULT_PORT);
 client.send(message);
 waiting++;
 times++;
 Thread.sleep(SLEEPING);
 System.out.println("Thread = " + counter+" has status "+status+" with ID "+threadID);
 if(newlead==2){
 System.out.println("New leader and subleader are found.Thank you.");
 break;
 if(status=="LEADER"){
 str=""+12345+counter;
 strn = str.getBytes();
 message = new DatagramPacket(strn, strn.length,groupp,DEFAULT_PORT);
 client.send(message);
 if(status=="subLEADER"){
 str=""+123456+counter;
 strn = str.getBytes();
 message = new DatagramPacket(strn, strn.length,groupp,DEFAULT_PORT);
 client.send(message);
 Thread.sleep(SLEEPING);
 if(done2==false){
 done=false;
 } catch(IOException e){System.out.println(e);}
catch(NumberFormatException e){System.out.println(e);}
 catch(InterruptedException e){System.out.println(e);}

Multicast transmission problem

Hi,
I'm tring to multicast audio streams from 1 computer to another on the same network. The multicast address for my network is 10.255.255.255. When I check the amount of transmission bytes from ifconfig continually, I see a gradual increase of bytes being sent out to the network.
When I look at ifconfig on the receiving computer, it is receiving bytes as well. But AVReceive2 can't detect the rtp stream. It just keeps on waiting for the data to come. By the way, I use AVTransmit2 to transmit the data. But when I just unicast the rtp stream from one computer to another, then the rtp streaming works!!
Anyone has the same problem as me. Can anyone point out any problems that I may be having. Oh yeah and I am running JMF between two red hat linux 9 notebooks.
Do I have to do some extra modification to some ip routing table somewhere or sonething?
Thanks to anybody that can PLEASE help me!!!1

Hi Stefan,
If I unicast an audio file from one computer to the other then it works fine. I didn't try sending a video file but I think it should work the same as well. I've got two computers, one having an ip address of 10.0.0.1 and the other having an ip address of 10.0.0.2. Doing an ifconfig, my broadcast address on each computer is stated as 10.255.255.255. When I use 10.255.255.255 to send my audio file, using ifconfig again, I notice that the receiving computer is receving bytes but the program isn't recognising the rtp stream. My program uses a similar address resolution to avtransmit2 and avreceive2.
So I can't figure out what's wrong with the code. Ok for avreceive2, what do you usually type in the command line to receive broadcast packets? Do we have to modify the /etc/hosts file again??
Thanks

Multicast stream problem with windows media service

Hi,
I'm on a simple LAN composed by cisco 3560G and 3750G switches. On one of my switches, i've connected a windows media server that stream tv in unicast and multicast mode.
When i run the http://myserver/mystream.nsc generated by the server on the current server, it's working, i can see my stream. The problem is in the stations, i'm unable to see it.
I've activated IGMP Snooping on each switchs.
Here is the log of debug ip igmp snooping on the switch where the server is connected :
3750G#
Dec 4 18:32:52.882 GMT+1: IGMPSN: group: Received V2 report for group 239.192.39.139 received on Vlan 1, port Gi1/0/3
Dec 4 18:32:52.882 GMT+1: IGMPSN: group: Adding client ip 10.10.10.10, port_id Gi1/0/3, on vlan 1
Dec 4 18:32:52.882 GMT+1: IGMPSN: mgt: created group EFC0278B, on Vlan 1
Dec 4 18:32:55.147 GMT+1: IGMPSN: Received SVI query(224.0.0.1) on vlan 1
Dec 4 18:32:55.147 GMT+1: IGMPSN: Adding iquerier flag in vlan 1
Dec 4 18:32:55.147 GMT+1: IGMPSN: router: iquerier added on Vlan 1
Dec 4 18:32:57.907 GMT+1: IGMPSN: group: Received V2 report for group 239.192.39.139 received on Vlan 1, port Gi1/0/3
Dec 4 18:32:57.907 GMT+1: IGMPSN: group: Adding client ip 10.10.10.10, port_id Gi1/0/3, on vlan 1
Dec 4 18:33:00.852 GMT+1: IGMPSN: group: Received V2 report for group 225.10.10.10 received on Vlan 1, port Gi1/0/2
Dec 4 18:33:05.155 GMT+1: IGMPSN: timer: Vlan 1 report timer expired
Dec 4 18:33:14.769 GMT+1: IGMPSN: group: Leave for group 239.192.39.139 received on Vlan 1, port Gi1/0/3
Dec 4 18:33:14.769 GMT+1: IGMPSN: group: Adding client ip 10.10.10.10, port_id Gi1/0/3, on vlan 1
Dec 4 18:33:14.769 GMT+1: IGMPSN: group: Sending Group-Specific Query for group 239.192.39.139 on Vlan 1, port Gi1/0/3
Dec 4 18:33:15.775 GMT+1: IGMPSN: timer: Vlan 1, group 239.192.39.139, port Gi1/0/3 leave port timer expired
Dec 4 18:33:15.775 GMT+1: IGMPSN: group: Deleting group 239.192.39.139
Dec 4 18:33:15.775 GMT+1: IGMPSN: group: Deleting gce 0100.5e40.278b
Dec 4 18:33:15.775 GMT+1: IGMPSN: group: Sending Leave for group 239.192.39.139, source 10.10.10.10 on Vlan 1
Dec 4 18:33:15.775 GMT+1: IGMPSN: Received SVI query(239.192.39.139) on vlan 1
Dec 4 18:33:15.775 GMT+1: IGMPSN: Adding iquerier flag in vlan 1
Dec 4 18:33:15.775 GMT+1: IGMPSN: router: iquerier added on Vlan 1
Dec 4 18:33:16.782 GMT+1: IGMPSN: Received SVI query(239.192.39.139) on vlan 1
Dec 4 18:33:16.782 GMT+1: IGMPSN: Adding iquerier flag in vlan 1
Dec 4 18:33:16.782 GMT+1: IGMPSN: router: iquerier added on Vlan 1
3750G#
3750G#sh ip igmp groups
IGMP Connected Group Membership
Group Address Interface Uptime Expires Last Reporter
239.192.39.139 Vlan1 00:00:03 00:02:56 10.10.10.10

As WMP is not a DVD player, my suggestion would be to tell your clients to never use WMP.All our DVD discs go out with a warning not to allow WMP to be used.
In most computer setups, WMP does not play back video correctly as it does not have an MPEG codec installed, or has navigational problems.
All computers that have a DVD drive fitted, will have a dedicated DVD software player installed, such as Win DVD or Power DVD, so why not use that?

Seeburger - async receiving MDN problem- no binding found for AS2

Hi guys!
We have configured AS2 receiver adapter but during receiveing Async MDN we get following error (sending of message is successful) :
Cannot receive async MDN: com.seeburger.as2.exception.AS2PluginException: Inbound communication from 90586 to 22266 not allowed: com.seeburger.conf.BackingStoreException: Unable to execute query because: com.seeburger.xi.config.ConfigException: No binding found for: AS2, http://seeburger.com/xi, Gloria, R3
Note: Gloria & R3 are names of XI identifiers (scheme: XIParty) and 22266 & 90586 are names from AS2ID scheme - alternative identifiers.
22266 - is sender of original message
90586 - is receiver
What is wrong on the settings? Why the sending message uses alternative identifiers and incoming MDN does not?
Thanx for answers & suggestions!
Peter

Hi Peter
checkm this thread discuss the same ..... hope it will solve ur all querry
Seeburger AS2 Adapter No binding found for: AS2, http://seeburger.com/xi
Thanks !!!
Questions are welcome here!!
Also mark helpful answers by rewarding points
Thanks,
Abhishek Agrahari

Potential dynamic server list updating problem in cluster

We are running a cluster of four Windows 2000 Server boxes under WLS
 6.1SP2. We have seen the following behavior in our cluster. We shutdown
 a cluster member and then bring it back up. When it comes back up, the
 IIS plug-in seems to start routing all requests to that new server.
 Out cluster seems to have some multicast connectivity problems, e.g. we
 often cannot see managed servers on the admin. console, etc. What I'm
 wondering is whether the server when it comes up could be telling IIS
 that it is the only cluster member because it isn't aware of any other
 members. This would explain the plug-ins sudden affinity for the new server.
 Is this possible? Has anyone seen this?
 Thanks in advance,
 Coty
 P.S. The box that is being restarted and then hogging the requests is
 also the server where the admin. console is running. Could that be the
 issue? What exactly are the implications of running a managed server and
 the admin. console on one box?


Is it that the admin server is also part of the cluster and is the server
 that is being restarted?
 Try to have the admin server for purely administrative tasks and not as part
 of a working cluster.
 If you have Debug set to ON in the plugin end, try checking the server list
 http://IISServer:port/dummyQuery?__WebLogicBridgeConfig
 This should return the dynamic and static server list that the IIS proxy is
 supposed to forward.
 Check before restart and after restart.
 Also contact support to get the newest ISAPI plugin that contains latest
 fixes.
 -Sabha
 "Coty Rosenblath" <[email protected]> wrote in message
 news:[email protected]...
 > We are running a cluster of four Windows 2000 Server boxes under WLS
 > 6.1SP2. We have seen the following behavior in our cluster. We shutdown
 > a cluster member and then bring it back up. When it comes back up, the
 > IIS plug-in seems to start routing all requests to that new server.
 >
 > Out cluster seems to have some multicast connectivity problems, e.g. we
 > often cannot see managed servers on the admin. console, etc. What I'm
 > wondering is whether the server when it comes up could be telling IIS
 > that it is the only cluster member because it isn't aware of any other
 > members. This would explain the plug-ins sudden affinity for the new
 server.
 >
 > Is this possible? Has anyone seen this?
 >
 > Thanks in advance,
 > Coty
 >
 > P.S. The box that is being restarted and then hogging the requests is
 > also the server where the admin. console is running. Could that be the
 > issue? What exactly are the implications of running a managed server and
 > the admin. console on one box?
 >

Jrockit multicast bug on RHEL4, WLS cluster does not works!

OS and Kernel Version: Linux achilles1 2.6.9-34.0.1.ELsmp #1 SMP Wed May 17 16:59:36 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
We use Bea Weblogic 8.1SP5 with Jrockit JVM 1.4.2 on RHEL3. We upgraded to operating system to RHEL4, and found that the interface binding for multicast communication does not bind to the correct interface, it is always using the default interface. We tried it from a sample program, and found that the error is in the JVM.
This is a critical error for us, because our application server cluster use multicast for cluster communication.
No error msg. It seems like this BUG:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4082533 but it is solved.
List steps to reproduce the problem:
socket = new MulticastSocket(i);
if(s2 != null)
try
InetAddress inetaddress = InetAddress.getByName(s2);
System.out.println("Using interface at " + inetaddress.getHostAddress());
socket.setInterface(inetaddress);
System.out.println(socket.getInterface());
catch(SocketException socketexception)
throw socketexception;
}

Helo,
You can reproduce it by this way (we have 6 RHEL4 servers, problem is the same). We tried with programs written in C (mcast,Tibco), multicast perfectly works on all interfaces on all servers. But in Java:
Server:
[wlxapp@webex3]$ uname -a
Linux webex3 2.6.9-34.0.1.ELsmp #1 SMP Wed May 17 17:05:24 EDT 2006 i686 i686 i386 GNU/Linux
Problem - with Bea mukticast tester (or any Java class), using the nondefault webex3-priv interface(eth1):
[wlxapp@webex3]$ java -cp wl9.jar utils.MulticastTest -N webex3_priv -I webex3_priv -A 224.1.1.11 Starting test. Hit any key to abort Using interface at 192.168.1.1 Using multicast address 224.1.1.11:7001 Will send messages under the name webex3_priv every 2 seconds Will print warning every 600 seconds if no messages are received
I (webex3_priv) sent message num 1
I (webex3_priv) sent message num 2
I (webex3_priv) sent message num 3
Did not receive any message.
But if we use the default webex3 interface (eth0)
[wlxapp@webex3]$ java -cp wl9.jar utils.MulticastTest -N webex3 -I webex3 -A 224.1.1.11 Starting test. Hit any key to abort Using interface at 10.4.20.4 Using multicast address 224.1.1.11:7001 Will send messages under the name webex3 every 2 seconds Will print warning every 600 seconds if no messages are received
I (webex3) sent message num 1
I (webex3) sent message num 2 Received message 2 from webex3
I (webex3) sent message num 3 Received message 3 from webex3
Works perfectly.
TCPDUMP:Messages are out from server(other srv also see it), so we have problems probably with receiving them:
[root@webex3]# tcpdump -i eth1
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes
11:42:56.647362 IP webex3_priv.idmz.t-mobile.intra.afs3-callback > 224.1.1.111.afs3-callback: rx type 95 (1472)
11:42:56.648168 IP webex3_priv.idmz.t-mobile.intra > 224.1.1.111: udp
11:42:56.648245 IP webex3_priv.idmz.t-mobile.intra > 224.1.1.111: udp
We examined the lsof output, the tester bind to all interfaces, so it should receive the messages:
[wlxapp@webex3]$ /usr/sbin/lsof -p 11127
gij 11127 wlxapp 8u IPv4 150320 UDP *:afs3-callback
We tried the test with Java 1.4.2 and 1.5 (Jrockit and Sun), the results are the same.
You can easily reproduce the problem with an RHEL4 server with 2 network interface.
Our real problem that if multicast have problems, our Weblogic clusters does not works.

Seeburger: No matching inbound binding

Hi guys,
I'm having the following error :
I'm using Seeburger AS2 adapter and I'm trying to receive a message from an external partner. I've created the corresponding channels, sender and receiver agreements but I'm getting the following error:
No matching inbound binding (message) found for
FromParty:XITest ToParty:B2BTEST subject:1209234884433
I've set on the sender cchannel the 'AS2 message subject' as 'AS2 message test' and I think the problem is related to this configuration.
So I changed the value of the field to '*' so that I'm able to catch any subjects, like the one above....
But with this configuration '*', after activating the channel I'me getting a similar error on the 'communication channel monitoring' but with new subjects and with no party entities every 2 seconds...
No matching inbound binding (report) found for FromParty: ToParty: subject:
I've checked the threads
Seeburger - async receiving MDN problem- no binding found for AS2 from Peter and
Seeburger AS2 Adapter No binding found for: AS2, http://seeburger.com/xi from Murali but nothing....
Do you have any ideas?

Hi Prateek,
I'd already tried cleaning caches but no good...
Hi Peter,
I've found out what the problem was. What is the purpose of the flag 'Hostname check'? I'd the flag checked by default, I've unchecked it and now I'm able to receive the messages.
Answering your questions, yes, both are using parties and for the MDN i only have the sender agreement and not the receiver.
I'm sure I'll keep posting doubts in the next few days.
Thanks for your attention and patience

Ip igmp snooping querier?

i've been reading these forums and noticed that lot of people have problems with configuring multicast. basicly, problems are flooding bandwidth, no querier, confusing pim router configuration ...
also, ive seen some promisses from tehnical stuff that next gen of linksys switches will have #ip igmp snooping querier, like cat ones have. so i'm interested if someone can give me the answer.
it is interesting question for many people who would cant afford expensive cat switches for such simple usage.
regards,
david

Hi David,
You actually have a lot more options as seen in the GUI, so I though I would put as simple network together and run you through a validation.
But I am assuming you have the refreshed version of the SRW224G4P switch called the SRW224G4P-K9-NA .
If you have the old switch the following is not relevant to you.
I put together a simple network diagram showing my simple network topology used during my wee test;
I chose the RV042 as my Layer 3 router in this network.
It really was to provide DHCP services, but shortly after all devices had IP addresses, I removed the RV042, becauise I noticed it was sending out IP IGMP general queries.    Something I didn;t want in the following test.
I was using a software based multicast tester, produced by the wonderful folk at Twisted Pair Solutions. This software can either send and/or receive multicasts of a defined group and responds appropriately to IGMP General queries. I will call this software MCT (Multicast test).
I had the MCT software on PC C. PC C is plugged into switch port 10 It is sending multicasts into the switch at a rate of about 10 multicast packets a second.
I had the MCT software on PC A. PC A is plugged into switch port 1. It is set to receiving and count multicasts from the switch
I had PC B plugged into switch port 2. PC B is checking switch statistics, but not try to receive multicasts from PC 3.
I had setup multicast snooping on VLAN 1 and querying according to the GUI screen capture below.
Note: I only had a single vlan on this switch.
In a composite of two screen captures below, you can see that IGMP querier status is enabled.
I took off the RV042 out of the network, because i noticed within a wireshark capture on PC A,   that the RV042 was sending out group general queries. I wanted the switch to take over that role
I waited a few minutes, and displayed only igmp activity.
It can be clearly seen in the screen capture below;
SG300 series switch was sending out general queries (2 minutes) from source IP address 172.16.1.100.
It waited for the mcast router general query, but when none came, 60 seconds later sent out it's own general query. Fair enough, it had to assume a mcast router might be sending general queries every minute.
Switch statistics can be seen below, it showed;
that PC B on switch port G2 was not being flooded by multicasts, in other words snooping is working;
Port 10, PC C is sending in 2962 multicast packets to the switch.
Port 1,   PC A is receiving 2900 multicast packets from the switch
port 2 ,   PC B is not part of the multicast group 234.55.66.77 and as such is not being flooded by multicasts.
ALL three PCs are windows based products, and certain multicasts emanate from these devices.
show interafce count
      Port       InUcastPkts InMcastPkts InBcastPkts    InOctets
      gi1             12           9            6           3493
      gi2            247          237           6          43733
      gi3             0            0            0            0
      gi4             0            0            0            0
      gi5             0            0            0            0
      gi6             0            0            0            0
      gi7             0            0            0            0
      gi8             0            0            0            0
      gi9             0            0            0            0
      gi10            26          2962          3          850881
      gi11            0            0            0            0
      gi12            0            0            0            0
      gi13            0            0            0            0
      gi14            0            0            0            0
      gi15            0            0            0            0
      gi16            0            0            0            0
      gi17            0            0            0            0
      gi18            0            0            0            0
      gi19            0            0            0            0
      gi20            0            0            0            0
      gi21            0            0            0            0
      gi22            0            0            0            0
      gi23            0            0            0            0
      gi24            0            0            0            0
      gi25            0            0            0            0
      gi26            0            0            0            0
      gi27            0            0            0            0
      gi28            0            0            0            0
      Port       OutUcastPkts OutMcastPkts OutBcastPkts OutOctets
      gi1             13         2900          9          839691
      gi2            233         343           9          90453
      gi3             0            0            0            0
      gi4             0            0            0            0
      gi5             0            0            0            0
      gi6             0            0            0            0
      gi7             0            0            0            0
      gi8             0            0            0            0
      gi9             0            0            0            0
      gi10            24          343           12         47165
      gi11            0            0            0            0
      gi12            0            0            0            0
      gi13            0            0            0            0
      gi14            0            0            0            0
      gi15            0            0            0            0
      gi16            0            0            0            0
      gi17            0            0            0            0
      gi18            0            0            0            0
      gi19            0            0            0            0
      gi20            0            0            0            0
      gi21            0            0            0            0
      gi22            0            0            0            0
      gi23            0            0            0            0
      gi24            0            0            0            0
      gi25            0            0            0            0
      gi26            0            0            0            0
      gi27            0            0            0            0
      gi28            0            0            0            0
If I look at the multicast groups within the switch, it show that only two ports were involved in multicast group 234.55.66.77. This is the correct behaviour.
switch4cf17c#sh ip igmp snooping group
Vlan   Group        Source        Include Ports        Exclude Ports     Comp.
       Address      Address                                              Mode
1    234.55.66.77 *            gi1,gi10                                  v2
1    239.255.255. *            gi1-2,gi10                                v2
     250
Just to complete the posting, here is the CLI command (highlighted) to enable the querier functionality within the switch;
[Kswitch4cf17c#sh run
bridge multicast filtering
ip igmp snooping
ip igmp snooping vlan 1
ip igmp snooping vlan 1 querier
interface vlan 1
ip address 172.16.1.100 255.255.255.0
exit
interface vlan 1
no ip address dhcp
exit
hostname switch4cf17c
no passwords complexity enable
no snmp-server server
ip telnet server
Hope this helps you and others
regards Dave

JNDI Names of JMS server's queue not replicating to cluster

 Am having some trouble configuring a JMS Server and Queues in a clustered development
 environment. It is a simple cluster of 2 servers (Server1 and Server2) both on
 a single machine.
 The "JobServer" JMS Server is targeted to "Server1 (migratable)". All the JNDI
 names for the Queues appear in the JNDI tree of Server1, but not in Server2.
 When the sending of a message is attempted on Server2, the following occurs:
 javax.naming.NameNotFoundException: While trying to lookup 'jms.STARSIIPostQueue'
 didn't find subcontext 'jms' Resolved ; remaining name 'jms/STARSIIPostQueue'
 at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:858)
 This may be a problem with the cluster configuration, but I haven't been able
 to see anything wrong with it.
 Any and all help will be appreciated.
 There is the Config.xml file:
 <?xml version="1.0" encoding="UTF-8"?>
 <Domain ConfigurationVersion="8.1.2.0" Name="mydomain">
 <Server ExtraEjbcOptions="-J-mx512m" ListenAddress=""
 ListenPort="7001" Name="myserver" NativeIOEnabled="true"
 ServerVersion="8.1.2.0" StdoutDebugEnabled="true" StdoutSeverityLevel="64">
 <SSL Enabled="false" HostnameVerificationIgnored="false"
 IdentityAndTrustLocations="KeyStores" ListenPort="7002" Name="myserver"/>
 <Log Name="myserver" NumberOfFilesLimited="true"/>
 </Server>
 <Security Name="mydomain"
 PasswordPolicy="wl_default_password_policy"
 Realm="wl_default_realm" RealmSetup="true">
 <weblogic.security.providers.authentication.DefaultAuthenticator
 Name="Security:Name=myrealmDefaultAuthenticator" Realm="Security:Name=myrealm"/>
 <weblogic.security.providers.authentication.DefaultIdentityAsserter
 ActiveTypes="AuthenticatedUser"
 Name="Security:Name=myrealmDefaultIdentityAsserter" Realm="Security:Name=myrealm"/>
 <weblogic.security.providers.authorization.DefaultRoleMapper
 Name="Security:Name=myrealmDefaultRoleMapper" Realm="Security:Name=myrealm"/>
 <weblogic.security.providers.authorization.DefaultAuthorizer
 Name="Security:Name=myrealmDefaultAuthorizer" Realm="Security:Name=myrealm"/>
 <weblogic.security.providers.authorization.DefaultAdjudicator
 Name="Security:Name=myrealmDefaultAdjudicator"
 Realm="Security:Name=myrealm" RequireUnanimousPermit="false"/>
 <weblogic.security.providers.credentials.DefaultCredentialMapper
 Name="Security:Name=myrealmDefaultCredentialMapper" Realm="Security:Name=myrealm"/>
 <weblogic.management.security.authentication.UserLockoutManager
 Name="Security:Name=myrealmUserLockoutManager" Realm="Security:Name=myrealm"/>
 <weblogic.management.security.Realm
 Adjudicator="Security:Name=myrealmDefaultAdjudicator"
 Auditors="Security:Name=myrealmSTARSIIAuditor"
 AuthenticationProviders="Security:Name=myrealmSTARSIIAuthenticator|Security:Name=myrealmDefaultAuthenticator|Security:Name=myrealmDefaultIdentityAsserter"
 Authorizers="Security:Name=myrealmDefaultAuthorizer|Security:Name=myrealmSTARSIIAuthorizer"
 CredentialMappers="Security:Name=myrealmDefaultCredentialMapper"
 DefaultRealm="true" DisplayName="myrealm"
 FullyDelegateAuthorization="true"
 Name="Security:Name=myrealm"
 RoleMappers="Security:Name=myrealmDefaultRoleMapper" UserLockoutManager="Security:Name=myrealmUserLockoutManager"/>
 <gov.fns.starsii.common.security.authentication.STARSIIAuthenticator
 ControlFlag="SUFFICIENT"
 Name="Security:Name=myrealmSTARSIIAuthenticator" Realm="Security:Name=myrealm"/>
 <gov.fns.starsii.common.security.authorization.STARSIIAuthorizer
 ExemptUri="/common/,/images/,/warning.do,/login.do"
 Name="Security:Name=myrealmSTARSIIAuthorizer"
 PolicyDeploymentEnabled="false"
 Realm="Security:Name=myrealm" Verbose="false" denyPermNotFound="true"/>
 <gov.fns.starsii.common.security.audit.STARSIIAuditor
 Name="Security:Name=myrealmSTARSIIAuditor" Realm="Security:Name=myrealm"/>
 </Security>
 <EmbeddedLDAP
 Credential="{3DES}aD+gV9rRggnoShH/kWurILaHTBP/z0jVoZHtp/hU1xI=" Name="mydomain"/>
 <SecurityConfiguration
 Credential="{3DES}mhxP4PeuUHmoX6Aggpj5SNB+AX16Gaol8dOfUzXu7xM8CFNASyNdYIOoqtlqPAZvfZgB14KBtY8MkdKGu/iWFq1xQ07walY8"
 Name="mydomain" RealmBootStrapVersion="1"/>
 <Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
 <FileRealm Name="wl_default_file_realm"/>
 <PasswordPolicy Name="wl_default_password_policy"/>
 <JDBCConnectionPool
 DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
 Name="STARSII BRSB Pool"
 Password="{3DES}9pslRpr051lR9/NEKdanag=="
 Properties="user=brsbapp;portNumber=1433;databaseName=brsbdev;serverName=str2-dev-db"
 Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
 <JDBCTxDataSource JNDIName="jdbc/StarsIIDS" Name="StarsIIDS"
 PoolName="STARSII Store Pool" Targets="MyCluster"/>
 <JDBCTxDataSource JNDIName="jdbc/TXStarsIIDS" Name="TXStarsIIDS"
 PoolName="STARSII Store Pool" Targets="MyCluster"/>
 
 <MailSession JNDIName="mail/STARSIIMailSession"
 Name="STARSIIMailSession" Properties="mail.host=str2-dev-prj" Targets="myserver"/>
 <JDBCConnectionPool
 DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
 Name="STARSII Store Pool"
 Password="{3DES}nKggeFT8wZkm0R9H8mXaEQ=="
 Properties="user=storeapp;portNumber=1433;databaseName=storedev;serverName=str2-dev-db"
 Targets="MyCluster"
 TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
 <JDBCConnectionPool
 DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
 Name="AffTest" Password=""
 Properties="user=sa;portNumber=1433;databaseName=affTest;serverName=AFRANK\AFRANK"
 Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://AFRANK\AFRANK:1433"/>
 <JDBCTxDataSource JNDIName="jdbc/AffTest" Name="AffTest"
 PoolName="AffTest" Targets=""/>
 <JDBCConnectionPool DriverName="weblogic.jdbcspy.SpyDriver"
 Name="Spy STARSII BRSB Pool"
 Password="{3DES}9pslRpr051lR9/NEKdanag=="
 Properties="user=brsbapp;portNumber=1433;databaseName=brsbdev;serverName=str2-dev-db"
 Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:spy:{jdbc:bea:sqlserver://str2-dev-db:1433};log=(file)C:\cvsrepo\sql.log"/>
 <JDBCConnectionPool
 DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
 Name="STARSII Store Pool 2"
 Password="{3DES}nKggeFT8wZkm0R9H8mXaEQ=="
 Properties="user=storeapp;portNumber=1433;databaseName=storedev;serverName=str2-dev-db"
 Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
 <JDBCTxDataSource JNDIName="jdbc/StarsIIDS2" Name="StarsIIDS2"
 PoolName="STARSII Store Pool" Targets=""/>
 <JDBCConnectionPool
 DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
 Name="STARSII Stars Pool"
 Password="{3DES}tjstL+8fUvdPQzqhNcCYGA=="
 Properties="user=starsapp;portNumber=1433;databaseName=stars;serverName=str2-dev-db"
 Targets="MyCluster"
 TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
 <Machine Name="MachineA">
 <NodeManager DebugEnabled="true" ListenPort="5555" Name="MachineA"/>
 </Machine>
 <Server Cluster="MyCluster" ExpectedToRun="false"
 ExtraEjbcOptions="-J-mx521m" JDBCLoggingEnabled="true"
 ListenAddress="10.0.0.14" ListenPort="7002" Machine="MachineA"
 Name="Server1" ServerVersion="8.1.2.0" StdoutDebugEnabled="true" StdoutSeverityLevel="64">
 <ServerDebug Name="Server1"/>
 <SSL IdentityAndTrustLocations="KeyStores" Name="Server1"/>
 <KernelDebug Name="Server1"/>
 <Log Name="Server1"/>
 <ServerStart Name="Server1"
 OutputFile="C:\bea\user_projects\domains\mydomain\.\NodeManagerClientLogs\mydomain_Server1\startServer_05_05_2004-12_50_56-4.log"
 Password="{3DES}js4NnTcuqRE15gEGfNTu4Q==" Username="system"/>
 <WebServer Name="Server1"/>
 <COM Name="Server1"/>
 <IIOP Name="Server1"/>
 <JTAMigratableTarget Name="Server1" UserPreferredServer="Server1"/>
 <JTARecoveryService Name="Server1"/>
 </Server>
 <Cluster ClusterAddress="10.0.0.14, 10.0.2.15"
 MulticastAddress="226.0.0.244" Name="MyCluster"/>
 <Server Cluster="MyCluster" ExpectedToRun="false"
 ExtraEjbcOptions="-J-mx521m" ListenAddress="10.0.2.15"
 ListenPort="7002" Machine="MachineB" Name="Server2"
 ServerVersion="8.1.2.0" StdoutDebugEnabled="true" StdoutSeverityLevel="64">
 <ServerDebug Name="Server2"/>
 <SSL IdentityAndTrustLocations="KeyStores" Name="Server2"/>
 <KernelDebug Name="Server2"/>
 <Log Name="Server2"/>
 <ServerStart Name="Server2"
 Password="{3DES}js4NnTcuqRE15gEGfNTu4Q==" Username="system"/>
 <WebServer Name="Server2"/>
 <COM Name="Server2"/>
 <IIOP Name="Server2"/>
 <JTAMigratableTarget Name="Server2" UserPreferredServer="Server2"/>
 <JTARecoveryService Name="Server2"/>
 </Server>
 <MigratableTarget Cluster="MyCluster" Name="Server1 (migratable)"
 Notes="This is a system generated default migratable target for a server.
 Do not delete manually." UserPreferredServer="Server1"/>
 <MigratableTarget Cluster="MyCluster" Name="Server2 (migratable)"
 Notes="This is a system generated default migratable target for a server.
 Do not delete manually." UserPreferredServer="Server2"/>
 <Application Deployed="true" Name="STARSII"
 Path="C:\cvsrepo\STARSII\STARSII" StagingMode="nostage" TwoPhase="true">
 <EJBComponent Name="../brsbMessage" Targets="MyCluster" URI="../brsbMessage"/>
 <EJBComponent Name="../brsbSession" Targets="MyCluster" URI="../brsbSession"/>
 <EJBComponent Name="../commonSession" Targets="MyCluster" URI="../commonSession"/>
 <EJBComponent Name="../complianceMessage" Targets="MyCluster" URI="../complianceMessage"/>
 <EJBComponent Name="../complianceSession" Targets="MyCluster" URI="../complianceSession"/>
 <EJBComponent Name="../starsiiEntity" Targets="MyCluster" URI="../starsiiEntity"/>
 <EJBComponent Name="../storeSession" Targets="MyCluster" URI="../storeSession"/>
 <WebAppComponent Name="/brsb" Targets="MyCluster" URI="../brsbWebApp"/>
 <WebAppComponent Name="/compliance" Targets="MyCluster" URI="../complianceWebApp"/>
 <WebAppComponent Name="/common" Targets="MyCluster" URI="../mainWebApp"/>
 <WebAppComponent Name="/store" Targets="MyCluster" URI="../storeWebApp"/>
 </Application>
 <Application Name="AffWebApp" Path="C:\cvsrepo\STARSII"
 StagingMode="nostage" TwoPhase="true">
 <WebAppComponent Name="AffWebApp" Targets="" URI="AffWebApp"/>
 </Application>
 <Application Name="activeportal"
 Path="C:\bea\user_projects\domains\mydomain\myserver\upload"
 StagingMode="nostage" TwoPhase="true">
 <WebAppComponent Name="activeportal" Targets="" URI="activeportal.war"/>
 </Application>
 <JTA Name="mydomain" TimeoutSeconds="300"/>
 <JMSServer Name="JobServer" Targets="Server1 (migratable)">
 <JMSQueue CreationTime="1072820642598"
 JNDIName="jms/STARSIIJobQueue" Name="STARSIIJobQueue"/>
 <JMSQueue CreationTime="1072820669345"
 JNDIName="jms/STARSIIPostQueue" Name="STARSIIPostQueue"/>
 <JMSQueue CreationTime="1088000795852"
 JNDIName="jms/STARSIIValidationQueue" Name="STARSIIValidationQueue"/>
 <JMSQueue CreationTime="1072820687125"
 JNDIName="jms/STARSIIErrorQueue" Name="STARSIIErrorQueue"/>
 <JMSQueue CreationTime="1072820687125"
 JNDIName="jms/STARSIIEmailQueue" Name="STARSIIEmailQueue"/>
 <JMSQueue CreationTime="1072820687225"
 JNDIName="jms/STARSIIEBTStateQueue" Name="STARSIIEBTStateQueue"/>
 <JMSQueue CreationTime="1072820687325"
 JNDIName="jms/STARSIIRFIQueue" Name="STARSIIRFIQueue"/>
 <JMSQueue CreationTime="1072820687425"
 JNDIName="jms/STARSIIRedeQueue" Name="STARSIIRedeQueue"/>
 <JMSQueue CreationTime="1072820687525"
 JNDIName="jms/STARSIIWatchListQueue" Name="STARIIWatchListQueue"/>
 <JMSQueue CreationTime="1072820687625"
 JNDIName="jms/STARSIIDeleteTransFileQueue" Name="STARSIIDeleteTransFileQueue"/>
 <JMSQueue CreationTime="1072820687725"
 JNDIName="jms/STARSIIUpdateAMRQueue" Name="STARSIIUpdateAMRQueue"/>
 <JMSQueue CreationTime="1072820687825"
 JNDIName="jms/STARSIIVPPExtractQueue" Name="STARSIIVPPExtractQueue"/>
 <JMSQueue CreationTime="1072820687925"
 JNDIName="jms/STARSIISIFSUploadQueue" Name="STARSIISIFSUploadQueue"/>
 <JMSQueue CreationTime="1072820688025"
 JNDIName="jms/STARSIIMARSQueue" Name="STARSIIMARSQueue"/>
 <JMSQueue CreationTime="1072820688125"
 JNDIName="jms/STARSIIFRBRichmondExtractQueue" Name="STARSIIFRBRichmondExtractQueue"/>
 <JMSQueue CreationTime="1072820688225"
 JNDIName="jms/STARSIICOTSExtractQueue" Name="STARSIICOTSExtractQueue"/>
 <JMSQueue CreationTime="1072820688325"
 JNDIName="jms/STARSIIVPPUploadQueue" Name="STARSIIVPPUploadQueue"/>
 </JMSServer>
 <Machine Name="MachineB">
 <NodeManager DebugEnabled="true" Name="MachineB"/>
 </Machine>
 </Domain>


Internally, many BEA developers and testers use various versions
 of XP with clustering on a daily basis. I don't know what
 is unique about your machine. I suggest raising the issue
 with customer support and/or posting to the clustering newsgroup...
 Andy Frank wrote:
 > It would seems that my OS and the MultiCast config are to blame. The MultiCast
 > test utility worked fine the Win2K machines I tried. Think I will take another
 > look at MS KB article 827536 and/or think about another dev OS.
 >
 > "Andy Frank" <[email protected]> wrote:
 >
 >>Tom,
 >>Thanks for this info.
 >>
 >>My servers don't look like they are running in different subnets (had
 >>a friend
 >>look this over and he concurs).
 >>
 >>My network admin says he hasn't blocked multicast traffic.
 >>
 >>I think the MultiCast test utility is telling me that I have some kind
 >>of multicast
 >>config problem. Output follows:
 >>
 >>------ Begin MultiCast test utility output: ------
 >>C:\bea\weblogic81\server\bin>java utils.MulticastTest -N server200 -A
 >>237.155.15
 >>5.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(DatagramSocket.java:680)
 >> 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
 >> I (server200) sent message num 12
 >>------ End MultiCast test utility output: ------
 >>
 >>No "Received message X from server200" messages. I think I need to look
 >>into
 >>configuring multicast communications on my OK (Windows XP Pro, ver 2002
 >>SP1).
 >>I did see MS KB article 827536 about "An IP multicast may not be sent
 >>correctly
 >
 >>from Windows XP or from Windows Server 2003" (I do have 2 network adapters),
 >
 >>but
 >>the resolution scared me some.
 >>
 >>Think I will try some things out on another OS and see what that gets
 >>me.
 >>
 >>Any other thoughts on this will be appreciated.
 >>
 >>
 >>Tom Barnes wrote:
 >>
 >>>I too suspect something is going wrong with clustering, I wonder
 >>>if the servers are running in different subnets (even though
 >>>they are on the same box) and/or your network admin has
 >>>blocked multicast traffic.
 >>>
 >>>The MultiCast test utility should help narrow things down:
 >>>
 >>>http://e-docs.bea.com/wls/docs81/admin_ref/utils.html#1199798
 >>>
 >>>Tom
 >>>
 >>>Andy Frank wrote:
 >>>
 >>>
 >>>>Am having some trouble configuring a JMS Server and Queues in a clustered
 >>>
 >>>development
 >>>
 >>>>environment. It is a simple cluster of 2 servers (Server1 and Server2)
 >>>
 >>>both on
 >>>
 >>>>a single machine.
 >>>>
 >>>>The "JobServer" JMS Server is targeted to "Server1 (migratable)".
 >>
 >>>All the JNDI
 >>>
 >>>>names for the Queues appear in the JNDI tree of Server1, but not in
 >>>
 >>>Server2.
 >>>
 >>>>When the sending of a message is attempted on Server2, the following
 >>>
 >>>occurs:
 >>>
 >>>>javax.naming.NameNotFoundException: While trying to lookup 'jms.STARSIIPostQueue'
 >>>>didn't find subcontext 'jms' Resolved ; remaining name 'jms/STARSIIPostQueue'
 >>>> at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:858)
 >>>>
 >>>>This may be a problem with the cluster configuration, but I haven't
 >>>
 >>>been able
 >>>
 >>>>to see anything wrong with it.
 >>>>
 >>>>Any and all help will be appreciated.
 >>>>
 >>>>There is the Config.xml file:
 >>>><?xml version="1.0" encoding="UTF-8"?>
 >>>><Domain ConfigurationVersion="8.1.2.0" Name="mydomain">
 >>>> <Server ExtraEjbcOptions="-J-mx512m" ListenAddress=""
 >>>> ListenPort="7001" Name="myserver" NativeIOEnabled="true"
 >>>> ServerVersion="8.1.2.0" StdoutDebugEnabled="true" StdoutSeverityLevel="64">
 >>>> <SSL Enabled="false" HostnameVerificationIgnored="false"
 >>>> IdentityAndTrustLocations="KeyStores" ListenPort="7002"
 >>>
 >>>Name="myserver"/>
 >>>
 >>>> <Log Name="myserver" NumberOfFilesLimited="true"/>
 >>>> </Server>
 >>>> <Security Name="mydomain"
 >>>> PasswordPolicy="wl_default_password_policy"
 >>>> Realm="wl_default_realm" RealmSetup="true">
 >>>> <weblogic.security.providers.authentication.DefaultAuthenticator
 >>>> Name="Security:Name=myrealmDefaultAuthenticator" Realm="Security:Name=myrealm"/>
 >>>>
 >>>> <weblogic.security.providers.authentication.DefaultIdentityAsserter
 >>>> ActiveTypes="AuthenticatedUser"
 >>>> Name="Security:Name=myrealmDefaultIdentityAsserter" Realm="Security:Name=myrealm"/>
 >>>> <weblogic.security.providers.authorization.DefaultRoleMapper
 >>>> Name="Security:Name=myrealmDefaultRoleMapper" Realm="Security:Name=myrealm"/>
 >>>> <weblogic.security.providers.authorization.DefaultAuthorizer
 >>>> Name="Security:Name=myrealmDefaultAuthorizer" Realm="Security:Name=myrealm"/>
 >>>> <weblogic.security.providers.authorization.DefaultAdjudicator
 >>>> Name="Security:Name=myrealmDefaultAdjudicator"
 >>>> Realm="Security:Name=myrealm" RequireUnanimousPermit="false"/>
 >>>> <weblogic.security.providers.credentials.DefaultCredentialMapper
 >>>> Name="Security:Name=myrealmDefaultCredentialMapper" Realm="Security:Name=myrealm"/>
 >>>> <weblogic.management.security.authentication.UserLockoutManager
 >>>> Name="Security:Name=myrealmUserLockoutManager" Realm="Security:Name=myrealm"/>
 >>>> <weblogic.management.security.Realm
 >>>> Adjudicator="Security:Name=myrealmDefaultAdjudicator"
 >>>> Auditors="Security:Name=myrealmSTARSIIAuditor"
 >>>> AuthenticationProviders="Security:Name=myrealmSTARSIIAuthenticator|Security:Name=myrealmDefaultAuthenticator|Security:Name=myrealmDefaultIdentityAsserter"
 >>>> Authorizers="Security:Name=myrealmDefaultAuthorizer|Security:Name=myrealmSTARSIIAuthorizer"
 >>>> CredentialMappers="Security:Name=myrealmDefaultCredentialMapper"
 >>>> DefaultRealm="true" DisplayName="myrealm"
 >>>> FullyDelegateAuthorization="true"
 >>>> Name="Security:Name=myrealm"
 >>>> RoleMappers="Security:Name=myrealmDefaultRoleMapper" UserLockoutManager="Security:Name=myrealmUserLockoutManager"/>
 >>>>
 >>>> <gov.fns.starsii.common.security.authentication.STARSIIAuthenticator
 >>>> ControlFlag="SUFFICIENT"
 >>>> Name="Security:Name=myrealmSTARSIIAuthenticator" Realm="Security:Name=myrealm"/>
 >>>> <gov.fns.starsii.common.security.authorization.STARSIIAuthorizer
 >>>> ExemptUri="/common/,/images/,/warning.do,/login.do"
 >>>> Name="Security:Name=myrealmSTARSIIAuthorizer"
 >>>> PolicyDeploymentEnabled="false"
 >>>> Realm="Security:Name=myrealm" Verbose="false" denyPermNotFound="true"/>
 >>>> <gov.fns.starsii.common.security.audit.STARSIIAuditor
 >>>> Name="Security:Name=myrealmSTARSIIAuditor" Realm="Security:Name=myrealm"/>
 >>>> </Security>
 >>>> <EmbeddedLDAP
 >>>> Credential="{3DES}aD+gV9rRggnoShH/kWurILaHTBP/z0jVoZHtp/hU1xI="
 >>>
 >>>Name="mydomain"/>
 >>>
 >>>> <SecurityConfiguration
 >>>> Credential="{3DES}mhxP4PeuUHmoX6Aggpj5SNB+AX16Gaol8dOfUzXu7xM8CFNASyNdYIOoqtlqPAZvfZgB14KBtY8MkdKGu/iWFq1xQ07walY8"
 >>>> Name="mydomain" RealmBootStrapVersion="1"/>
 >>>> <Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
 >>>> <FileRealm Name="wl_default_file_realm"/>
 >>>> <PasswordPolicy Name="wl_default_password_policy"/>
 >>>> <JDBCConnectionPool
 >>>> DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
 >>>> Name="STARSII BRSB Pool"
 >>>> Password="{3DES}9pslRpr051lR9/NEKdanag=="
 >>>> Properties="user=brsbapp;portNumber=1433;databaseName=brsbdev;serverName=str2-dev-db"
 >>>> Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects"
 >>>
 >>>URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
 >>>
 >>>> <JDBCTxDataSource JNDIName="jdbc/StarsIIDS" Name="StarsIIDS"
 >>>> PoolName="STARSII Store Pool" Targets="MyCluster"/>
 >>>> <JDBCTxDataSource JNDIName="jdbc/TXStarsIIDS" Name="TXStarsIIDS"
 >>>> PoolName="STARSII Store Pool" Targets="MyCluster"/>
 >>>> 
 >>>> <MailSession JNDIName="mail/STARSIIMailSession"
 >>>> Name="STARSIIMailSession" Properties="mail.host=str2-dev-prj"
 >>>
 >>>Targets="myserver"/>
 >>>
 >>>> <JDBCConnectionPool
 >>>> DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
 >>>> Name="STARSII Store Pool"
 >>>> Password="{3DES}nKggeFT8wZkm0R9H8mXaEQ=="
 >>>> Properties="user=storeapp;portNumber=1433;databaseName=storedev;serverName=str2-dev-db"
 >>>> Targets="MyCluster"
 >>>> TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
 >>>> <JDBCConnectionPool
 >>>> DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
 >>>> Name="AffTest" Password=""
 >>>> Properties="user=sa;portNumber=1433;databaseName=affTest;serverName=AFRANK\AFRANK"
 >>>> Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects"
 >>>
 >>>URL="jdbc:bea:sqlserver://AFRANK\AFRANK:1433"/>
 >>>
 >>>> <JDBCTxDataSource JNDIName="jdbc/AffTest" Name="AffTest"
 >>>> PoolName="AffTest" Targets=""/>
 >>>> <JDBCConnectionPool DriverName="weblogic.jdbcspy.SpyDriver"
 >>>> Name="Spy STARSII BRSB Pool"
 >>>> Password="{3DES}9pslRpr051lR9/NEKdanag=="
 >>>> Properties="user=brsbapp;portNumber=1433;databaseName=brsbdev;serverName=str2-dev-db"
 >>>> Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects"
 >>>
 >>>URL="jdbc:spy:{jdbc:bea:sqlserver://str2-dev-db:1433};log=(file)C:\cvsrepo\sql.log"/>
 >>>
 >>>> <JDBCConnectionPool
 >>>> DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
 >>>> Name="STARSII Store Pool 2"
 >>>> Password="{3DES}nKggeFT8wZkm0R9H8mXaEQ=="
 >>>> Properties="user=storeapp;portNumber=1433;databaseName=storedev;serverName=str2-dev-db"
 >>>> Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects"
 >>>
 >>>URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
 >>>
 >>>> <JDBCTxDataSource JNDIName="jdbc/StarsIIDS2" Name="StarsIIDS2"
 >>>> PoolName="STARSII Store Pool" Targets=""/>
 >>>> <JDBCConnectionPool
 >>>> DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
 >>>> Name="STARSII Stars Pool"
 >>>> Password="{3DES}tjstL+8fUvdPQzqhNcCYGA=="
 >>>> Properties="user=starsapp;portNumber=1433;databaseName=stars;serverName=str2-dev-db"
 >>>> Targets="MyCluster"
 >>>> TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
 >>>> <Machine Name="MachineA">
 >>>> <NodeManager DebugEnabled="true" ListenPort="5555" Name="MachineA"/>
 >>>> </Machine>
 >>>> <Server Cluster="MyCluster" ExpectedToRun="false"
 >>>> ExtraEjbcOptions="-J-mx521m" JDBCLoggingEnabled="true"
 >>>> ListenAddress="10.0.0.14" ListenPort="7002" Machine="MachineA"
 >>>> Name="Server1" ServerVersion="8.1.2.0" StdoutDebugEnabled="true"
 >>>
 >>>StdoutSeverityLevel="64">
 >>>
 >>>> <ServerDebug Name="Server1"/>
 >>>> <SSL IdentityAndTrustLocations="KeyStores" Name="Server1"/>
 >>>> <KernelDebug Name="Server1"/>
 >>>> <Log Name="Server1"/>
 >>>> <ServerStart Name="Server1"
 >>>> OutputFile="C:\bea\user_projects\domains\mydomain\.\NodeManagerClientLogs\mydomain_Server1\startServer_05_05_2004-12_50_56-4.log"
 >>>> Password="{3DES}js4NnTcuqRE15gEGfNTu4Q==" Username="system"/>
 >>>> <WebServer Name="Server1"/>
 >>>> <COM Name="Server1"/>
 >>>> <IIOP Name="Server1"/>
 >>>> <JTAMigratableTarget Name="Server1" UserPreferredServer="Server1"/>
 >>>> <JTARecoveryService Name="Server1"/>
 >>>> </Server>
 >>>> <Cluster ClusterAddress="10.0.0.14, 10.0.2.15"
 >>>> MulticastAddress="226.0.0.244" Name="MyCluster"/>
 >>>> <Server Cluster="MyCluster" ExpectedToRun="false"
 >>>> ExtraEjbcOptions="-J-mx521m" ListenAddress="10.0.2.15"
 >>>> ListenPort="7002" Machine="MachineB" Name="Server2"
 >>>> ServerVersion="8.1.2.0" StdoutDebugEnabled="true" StdoutSeverityLevel="64">
 >>>> <ServerDebug Name="Server2"/>
 >>>> <SSL IdentityAndTrustLocations="KeyStores" Name="Server2"/>
 >>>> <KernelDebug Name="Server2"/>
 >>>> <Log Name="Server2"/>
 >>>> <ServerStart Name="Server2"
 >>>> Password="{3DES}js4NnTcuqRE15gEGfNTu4Q==" Username="system"/>
 >>>> <WebServer Name="Server2"/>
 >>>> <COM Name="Server2"/>
 >>>> <IIOP Name="Server2"/>
 >>>> <JTAMigratableTarget Name="Server2" UserPreferredServer="Server2"/>
 >>>> <JTARecoveryService Name="Server2"/>
 >>>> </Server>
 >>>> <MigratableTarget Cluster="MyCluster" Name="Server1 (migratable)"
 >>>> Notes="This is a system generated default migratable target
 >>>
 >>>for a server.
 >>>
 >>>>Do not delete manually." UserPreferredServer="Server1"/>
 >>>> <MigratableTarget Cluster="MyCluster" Name="Server2 (migratable)"
 >>>> Notes="This is a system generated default migratable target
 >>>
 >>>for a server.
 >>>
 >>>>Do not delete manually." UserPreferredServer="Server2"/>
 >>>> <Application Deployed="true" Name="STARSII"
 >>>> Path="C:\cvsrepo\STARSII\STARSII" StagingMode="nostage" TwoPhase="true">
 >>>> <EJBComponent Name="../brsbMessage" Targets="MyCluster" URI="../brsbMessage"/>
 >>>> <EJBComponent Name="../brsbSession" Targets="MyCluster" URI="../brsbSession"/>
 >>>> <EJBComponent Name="../commonSession" Targets="MyCluster"
 >>
 >>URI="../commonSession"/>
 >>
 >>>> <EJBComponent Name="../complianceMessage" Targets="MyCluster"
 >>>
 >>>URI="../complianceMessage"/>
 >>>
 >>>> <EJBComponent Name="../complianceSession" Targets="MyCluster"
 >>>
 >>>URI="../complianceSession"/>
 >>>
 >>>> <EJBComponent Name="../starsiiEntity" Targets="MyCluster"
 >>
 >>URI="../starsiiEntity"/>
 >>
 >>>> <EJBComponent Name="../storeSession" Targets="MyCluster" URI="../storeSession"/>
 >>>> <WebAppComponent Name="/brsb" Targets="MyCluster" URI="../brsbWebApp"/>
 >>>> <WebAppComponent Name="/compliance" Targets="MyCluster" URI="../complianceWebApp"/>
 >>>> <WebAppComponent Name="/common" Targets="MyCluster" URI="../mainWebApp"/>
 >>>> <WebAppComponent Name="/store" Targets="MyCluster" URI="../storeWebApp"/>
 >>>> </Application>
 >>>> <Application Name="AffWebApp" Path="C:\cvsrepo\STARSII"
 >>>> StagingMode="nostage" TwoPhase="true">
 >>>> <WebAppComponent Name="AffWebApp" Targets="" URI="AffWebApp"/>
 >>>> </Application>
 >>>> <Application Name="activeportal"
 >>>> Path="C:\bea\user_projects\domains\mydomain\myserver\upload"
 >>>> StagingMode="nostage" TwoPhase="true">
 >>>> <WebAppComponent Name="activeportal" Targets="" URI="activeportal.war"/>
 >>>> </Application>
 >>>> <JTA Name="mydomain" TimeoutSeconds="300"/>
 >>>> <JMSServer Name="JobServer" Targets="Server1 (migratable)">
 >>>> <JMSQueue CreationTime="1072820642598"
 >>>> JNDIName="jms/STARSIIJobQueue" Name="STARSIIJobQueue"/>
 >>>> <JMSQueue CreationTime="1072820669345"
 >>>> JNDIName="jms/STARSIIPostQueue" Name="STARSIIPostQueue"/>
 >>>> <JMSQueue CreationTime="1088000795852"
 >>>> JNDIName="jms/STARSIIValidationQueue" Name="STARSIIValidationQueue"/>
 >>>> <JMSQueue CreationTime="1072820687125"
 >>>> JNDIName="jms/STARSIIErrorQueue" Name="STARSIIErrorQueue"/>
 >>>> <JMSQueue CreationTime="1072820687125"
 >>>> JNDIName="jms/STARSIIEmailQueue" Name="STARSIIEmailQueue"/>
 >>>> <JMSQueue CreationTime="1072820687225"
 >>>> JNDIName="jms/STARSIIEBTStateQueue" Name="STARSIIEBTStateQueue"/>
 >>>> <JMSQueue CreationTime="1072820687325"
 >>>> JNDIName="jms/STARSIIRFIQueue" Name="STARSIIRFIQueue"/>
 >>>> <JMSQueue CreationTime="1072820687425"
 >>>> JNDIName="jms/STARSIIRedeQueue" Name="STARSIIRedeQueue"/>
 >>>> <JMSQueue CreationTime="1072820687525"
 >>>> JNDIName="jms/STARSIIWatchListQueue" Name="STARIIWatchListQueue"/>
 >>>> <JMSQueue CreationTime="1072820687625"
 >>>> JNDIName="jms/STARSIIDeleteTransFileQueue" Name="STARSIIDeleteTransFileQueue"/>
 >>>> <JMSQueue CreationTime="1072820687725"
 >>>> JNDIName="jms/STARSIIUpdateAMRQueue" Name="STARSIIUpdateAMRQueue"/>
 >>>> <JMSQueue CreationTime="1072820687825"
 >>>> JNDIName="jms/STARSIIVPPExtractQueue" Name="STARSIIVPPExtractQueue"/>
 >>>> <JMSQueue CreationTime="1072820687925"
 >>>> JNDIName="jms/STARSIISIFSUploadQueue" Name="STARSIISIFSUploadQueue"/>
 >>>> <JMSQueue CreationTime="1072820688025"
 >>>> JNDIName="jms/STARSIIMARSQueue" Name="STARSIIMARSQueue"/>
 >>>> <JMSQueue CreationTime="1072820688125"
 >>>> JNDIName="jms/STARSIIFRBRichmondExtractQueue" Name="STARSIIFRBRichmondExtractQueue"/>
 >>>> <JMSQueue CreationTime="1072820688225"
 >>>> JNDIName="jms/STARSIICOTSExtractQueue" Name="STARSIICOTSExtractQueue"/>
 >>>> <JMSQueue CreationTime="1072820688325"
 >>>> JNDIName="jms/STARSIIVPPUploadQueue" Name="STARSIIVPPUploadQueue"/>
 >>>> </JMSServer>
 >>>> <Machine Name="MachineB">
 >>>> <NodeManager DebugEnabled="true" Name="MachineB"/>
 >>>> </Machine>
 >>>></Domain>
 >>>
 >

Problem with receiving of the UDP multicasting on multiple interfaces in the W2K12 cluster

Hi,
I have my .NET application which receives the UDP multicasting communication. It works fine until it is deployed on a W2K12 cluster. Some multicast groups are still available and some are not in the cluster. The
problem is caused by the cluster which creates a virtual interface for a inter-node communication. When the cluster is on and my app is trying to subscibe to the affected group then IGMP packets are routed to the cluster's
virtual interface where the multicast communication is not available. When the cluster (cluster service) is off all groups are available and IGMP is routed to a right interface.
I also have a different application which is not based on .NET and it receives all multicast groups in any deployment (same W2K12 clustered server). So, I guess that in my app I have to tell to the socket somehow, which local interface should
be used for a particular multicast group. In my app I use code below for a group subscribtion, but I still can't manage routing of IGMP to a right local interface. Can you help me?
As you can see in the code example I try to mapp a group to a local interface using its IP and index using MulticastOption class, but it has no effect. Different interface (cluster's virtual interface) is used for a IGMP
subscribtion. I also tried to bind\set local interface to Any, but without success.
It seems that there is some OS logic which overrides my setup. But, it must be possible to do the socket setup correctlly because non .NET application works fine.
Thanks.
Regards,
Marek
public void Start(string[] args)
//args[0] - multicast group
//args[1] - multicast port
//args[2] - local interface IP
//args[3] - local interface index
UdpClient udp = new UdpClient();
udp.Client.SetSocketOption(SocketOptionLevel.Socket, SocketOptionName.ReuseAddress, true);
udp.Client.Bind(new IPEndPoint(IPAddress.Parse(args[2]), Convert.ToInt32(args[1])));
MulticastOption mcastOption = new MulticastOption(IPAddress.Parse(args[0]));
mcastOption.LocalAddress = IPAddress.Parse(args[2]);
mcastOption.InterfaceIndex = int.Parse(args[3]);
udp.Client.SetSocketOption(SocketOptionLevel.IP, SocketOptionName.AddMembership, mcastOption);
udp.BeginReceive(new AsyncCallback(Receive), udp);

I don’t know if it will help you but I can illustrate my problem on the following prints from netsh and route tools. First print from netsh shows that the affected group 224.0.46.232 is assigned to interface 20. Second print shows
that interface 20 is Microsoft Failover Cluster Virtual Adapter where multicast communication is not available.
When the test app, which works fine, is used than these prints show that group 224.0.46.232 is assigned to interface 19 - Microsoft Network Adapter Multiplexor Driver, where multicast communication is available.
So, the question is how to manage these „prints“ to requested setup in .NET.
Regards,
Marek
C:\Windows\system32>netsh interface ip show joins
Interface 1: Loopback Pseudo-Interface 1
Scope       References Last Address
0                    0 Yes   239.255.255.250
Interface 20: Local Area Connection* 12
Scope       References Last Address
0                    0 Yes   224.0.0.1
0                    1 Yes   224.0.0.252
0                    1 Yes   224.0.46.232
Interface 19: Public
Scope       References Last Address
0                    0 No    224.0.0.1
0                    1 No    224.0.0.252
0                    0 Yes   239.255.255.250
C:\Windows\system32>route print
===========================================================================
Interface List
19...3c d9 2b ef 8a ec ......Microsoft Network Adapter Multiplexor Driver
20...02 91 08 09 1a ae ......Microsoft Failover Cluster Virtual Adapter
1...........................Software Loopback Interface 1
16...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
21...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
===========================================================================

Airserver multicast mDNS problem

Similar Messages

Maybe you are looking for