You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2006/06/29 16:52:59 UTC

DO NOT REPLY [Bug 39931] New: - Using mcastBindAddress for Tomcat Clustering fails to receive multicast packets

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39931>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39931

           Summary: Using mcastBindAddress for Tomcat Clustering fails to
                    receive multicast packets
           Product: Tomcat 5
           Version: 5.5.12
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Catalina:Cluster
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: mdabbs@vibephone.com


With two systems, I tried to enable clustering so that sessions would replicate
in case of a failure on one of the systems.  The two systems have 3 network
cards in them.  eth2 goes to the NAS while eth1 and eth0 are on the main network
of other apache and tomcat servers.  eth0 is a backup for eth1 and is normally down.

The problem seems to be when I specify which interface to bind to in the
Membership node of server.xml.  If I specify
mcastBindAddress="<eth1-ip-address>", I can tell that Tomcat is listening and
sending on this address.  However, it seems that packets never get delivered to
the receive method in the McastServiceImpl class.  I've confirmed that the
multicast traffic reaches the machine but with debug logging on, I never get the
'mcast receive' log message.

If I remove the mcastBindAddress attribute from the Membership node in
server.xml, the multicast traffic gets delivered and session replication works.

On single-homed systems, it does not seem to matter if mcastBindAddress is set
or not - the multicast packets get delivered.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


DO NOT REPLY [Bug 39931] - Using mcastBindAddress for Tomcat Clustering fails to receive multicast packets

Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39931>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39931


fhanik@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO




------- Additional Comments From fhanik@apache.org  2006-06-29 16:54 -------
multicasting on a multihomed computer will require your routes to be setup
correctly on the box. I suggest using a tool like ethereal to debug where the
packets go, and report back to us, and we can address it then

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


DO NOT REPLY [Bug 39931] - Using mcastBindAddress for Tomcat Clustering fails to receive multicast packets

Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39931>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39931





------- Additional Comments From mdabbs@vibephone.com  2006-06-29 18:32 -------
I captured packets using tcpdump and opened the captured file using Ethereal. 
It shows that both machines do in fact receive the traffic.  The following is a
capture from 192.168.179.82:

No.     Time        Source                Destination           Protocol Len   
Cum.Len  Info
      1 0.000000    192.168.179.82        228.0.0.4             UDP      99    
99       Source port: 45564  Destination port: 45564
      2 0.353582    192.168.179.83        228.0.0.4             UDP      99    
198      Source port: 45564  Destination port: 45564
      3 0.509843    192.168.179.82        228.0.0.4             UDP      99    
297      Source port: 45564  Destination port: 45564
      4 0.863437    192.168.179.83        228.0.0.4             UDP      99    
396      Source port: 45564  Destination port: 45564
      5 1.019700    192.168.179.82        228.0.0.4             UDP      99    
495      Source port: 45564  Destination port: 45564
      6 1.373288    192.168.179.83        228.0.0.4             UDP      99    
594      Source port: 45564  Destination port: 45564
      7 1.529552    192.168.179.82        228.0.0.4             UDP      99    
693      Source port: 45564  Destination port: 45564
      8 1.883166    192.168.179.83        228.0.0.4             UDP      99    
792      Source port: 45564  Destination port: 45564
      9 2.039411    192.168.179.82        228.0.0.4             UDP      99    
891      Source port: 45564  Destination port: 45564
     10 2.392998    192.168.179.83        228.0.0.4             UDP      99    
990      Source port: 45564  Destination port: 45564


It appears to be a very similar, if not the same, issue as what is discussed at
the following thread:

http://marc.theaimsgroup.com/?l=tomcat-user&m=114020671804619&w=2

The network config:

eth0      Link encap:Ethernet  HWaddr 00:0A:5E:62:8A:7C
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:72 Base address:0x5000

eth1      Link encap:Ethernet  HWaddr 00:16:35:3C:7C:8C
          inet addr:192.168.179.82  Bcast:192.168.179.127  Mask:255.255.255.192
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:19735681 errors:0 dropped:0 overruns:0 frame:0
          TX packets:19618826 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3766136075 (3591.6 Mb)  TX bytes:2509851526 (2393.5 Mb)
          Interrupt:25

eth2      Link encap:Ethernet  HWaddr 00:16:35:3C:7C:8B
          inet addr:172.20.183.82  Bcast:172.20.183.127  Mask:255.255.255.128
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1095636 errors:0 dropped:0 overruns:0 frame:0
          TX packets:158700 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:90195462 (86.0 Mb)  TX bytes:32106664 (30.6 Mb)
          Interrupt:26

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:59811340 errors:0 dropped:0 overruns:0 frame:0
          TX packets:59811340 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:225325405 (214.8 Mb)  TX bytes:225325405 (214.8 Mb)


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


DO NOT REPLY [Bug 39931] - Using mcastBindAddress for Tomcat Clustering fails to receive multicast packets

Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39931>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39931


pr@objektpark.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |RESOLVED
         Resolution|                            |WORKSFORME




------- Additional Comments From pr@objektpark.de  2007-08-14 01:30 -------
This are not a tomcat cluster problem! It seem that network config is wrong.
Please give us more information, that we can simulate the problem.


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


DO NOT REPLY [Bug 39931] - Using mcastBindAddress for Tomcat Clustering fails to receive multicast packets

Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39931>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39931





------- Additional Comments From mdabbs@vibephone.com  2007-08-14 05:53 -------
Specifically what do you think is wrong about the network config? I will try to
provide more info in that area or any other that you think is related.

Filip mentioned that the routing may be set up wrong.  Here is the output of
route for the .82 machine:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.179.64  *               255.255.255.192 U     0      0        0 eth1
172.20.183.0    *               255.255.255.128 U     0      0        0 eth2
169.254.0.0     *               255.255.0.0     U     0      0        0 eth2
default         gs-dev-si1-int. 0.0.0.0         UG    0      0        0 eth1

If there is any other info I can provide, please let me know.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org