[
http://jira.jboss.com/jira/browse/JBAS-4939?page=comments#action_12386314 ]
Aleksandar Kostadinov commented on JBAS-4939:
---------------------------------------------
Ok, I did some more investigation and have some conclusions.
1. The initial issue of JBoss not seeing its own sent mcast messages appears to be that
dev90 needed a restart for unknown reason.
2. AFAICT there is no issue with the noip JBoss AS 5 hudson job. It fails but for other
reasons.
3. The mcast receiver test is reliable. We were misleaded by it failing on RHEL 4U5 and
above but clustering when one node is localhost and the other whatever IP works. Well taht
works because of the linux mcast behavior when 2 processes join the same mcast group/port
and on different interfaces. Effectively both receivers get mcast messages received
through both interfaces. So in this situatuin one node listens to localhost, one to eth0
thus both seeing each other.
Since this configuration is only a case when running the test suite we should not consider
mcast receiver test unreliable.
To see what I'm talking about do:
a> start a reveiver on lo
b> start a sender on lo
c> send a message (will be received on RHEL 4U4 but not on RHEL 4U5 and above)
d> start a receiver on eth0
e> send a message from the initial sender (will be received on both receiver ends)
I think that's all about this issue. Let me know if you want any additional
information.
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