[jboss-jira] [JBoss JIRA] Commented: (JBREM-876) Get Remoting testsuite to run in hudson
[ http://jira.jboss.com/jira/browse/JBREM-876?page=comments#action_12391727 ]
Ron Sigal commented on JBREM-876:
---------------------------------
The jgroups UDP protocol has a parameter "use_local_host", which, when set to
"false", causes it to bind to the first non-loopback address.
In jrunit, the jgroups configuration properties are configured in
org.jboss.jrunit.communication.MessageBus. The solution has two parts:
1. update jrunit.jar in Remoting so that it sets use_local_host to false, and
2. update the version of jgroups in Remoting to a version that supports the use_local_host
parameter.
The appropriate version of jgroups is JGroups-2.4.1.SP4, which is the newest version of
jgroups that does not require jdk 1.5.
Get Remoting testsuite to run in hudson
---------------------------------------
Key: JBREM-876
URL: http://jira.jboss.com/jira/browse/JBREM-876
Project: JBoss Remoting
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto)
The jrunit based Remoting tests are failing in hudson. The problem might be that jrunit
depends on multicasting in jgroups.
Aleksandar Kostadinov has said:
1. Let me know if it is related to multicast listener on lo and a multicast sender. There
is a change in behavior after RHEL 4.4 in that regard and I suspect that is the reason
tests to pass on the old build hosts and not on the new hudson ones.
2. How can we make it not bind to localhost? I don't think it will be possible to
have these passing without that. Will -Dbind_addr=something and -Dlocal_addr=something
change that or this has to be done in some property files as well?
--
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