[jboss-remoting-issues] [JBoss JIRA] Commented: (JBREM-1182) Update testsuite to run under Hudson

[ https://jira.jboss.org/jira/browse/JBREM-1182?page=com.atlassian.jira.plu... ] Richard Achmatowicz commented on JBREM-1182: -------------------------------------------- Just a couple of notes to myself concerning the JGroups configuration for JRunit. Might be of interest for others. 1. Independence of jrunit and test cases with respect to socket use The system properties jrunit.bind_addr, jrunit.mcast_addr, and runit.mcast_port are used by the JRunit framework to configure JGroups socket-based communication between the three processes in a JRunit test: TestDriver, TestClient and TestServer. TestClient and TestServer, in addition to containing part of the JRunit framework used for maintaining the JRunit lifecycle, will also contain test case code. Setting these values for JRunit is completely independent of any communication mechanisms used by the test cases TestClient and TestServer themselves. For example, JRunit may use (on Linux) the eth0 interface: jrunit.bind_addr=192.168.0.100 jrunit.mcast_addr=228.15.3.0 for communication between TestDriver, TestClient and TestSErver, and yet the TestClient and TestServer test case code may create sockets which only involve the loopback interface (127.0.0.1). Indeed, many Remoting test cases use localhost as a bind address when creating sockets and so make use of the loopback address 127.0.0.1. Thus, IP addresses used for test cases need not be related to the jrunit parameters mentioned above. Which is good. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira