[jboss-jira] [JBoss JIRA] Commented: (JBAS-4939) Hudson JBoss-AS-5.0.x-TestSuite-sun15-noip testsuite run does not complete

[Aleksandar Kostadinov (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBAS-4939?page=comments#action_12386080 ] 
            
Aleksandar Kostadinov commented on JBAS-4939:
---------------------------------------------

I think it is more than misconfiguration. 

Here is all information I have.

NOTE: JBoss 4.2 cluster tests pass even when one node is bound to localhost

So when JGroups joins a multicast group it creates a socket bound to the interface where the "-b" option argument resides. 
So running a server as "run -c all -b localhost" will bind the multicast socket to the local loopback interface and running with "run -c all -b `hostname`" will bind the socket to the eth0 interface (if we talk about a hudson slave). 

It appears that if multicast socket is bound to a network interface (being lo or eth#) which multicast route is not set through, then it cannot receive multicast messages. What was confusing and took much time to understand is that RHEL4 pre update 5 (<= RHEL 4U4) doesn't regard multicast routing and a listener to any interface receives multicast messages. RHEL 4U5 and RHEL5 however regard the multicast route and don't pass the message to the listener on any interface but that the multicast route goes through. 

Solutions:
1. Use only IPs on the same interface that multicast route goes through
2. Disable the default behavior to bind the socket to an interface but let OS choose the default one. If user forces the socket to be bound to specific interface, then bind to it. IMHO that is how things should work. And we will avoid the need user to mess with multicast configuration and adding IPs to be able to run the test  suite.

> Hudson JBoss-AS-5.0.x-TestSuite-sun15-noip testsuite run does not complete
> --------------------------------------------------------------------------
>
>                 Key: JBAS-4939
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4939
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>            Reporter: Dimitris Andreadis
>         Assigned To: Brian Stansberry
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> JBoss-AS-5.0.x-TestSuite-sun15-noip does not complete. After discussing the issue in the jboss-dev list, Brian found out the nodes are not configured properly.
> Open this JIRA case to make sure we follow up.
> Eventually, we should get rid of the 'noip' run.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira