[
https://jira.jboss.org/jira/browse/EJBTHREE-880?page=com.atlassian.jira.p...
]
Aleksandar Kostadinov commented on EJBTHREE-880:
------------------------------------------------
To be more precise, where I suggest you to select lo as an interface for multicast for
node1, you could try as well to specify eth0 as an mcast interface for node0. Since
interfaces are selected by IP, it should not be hard to tell node0 that it should use
node1's interface for jgroups.
Actually when I think more about it, it does make a great sense to have that done in every
clustering tests so they become really OS configuration independent!
Hard-coded localhost in ejb3 test suite
---------------------------------------
Key: EJBTHREE-880
URL:
https://jira.jboss.org/jira/browse/EJBTHREE-880
Project: EJB 3.0
Issue Type: Bug
Reporter: Aleksandar Kostadinov
Assignee: Juraci Paixao Krohling
Attachments: ejb3-4.0-testsuite Build Completed With Testsuite Errors.eml,
ejb3-4.2-testsuite Build Completed With Testsuite Errors.eml
When the ejb3 testsuite is run with "-Dnode0=IP1 -Dnode1=IP2" and
IP1!=localhost there are some tests failing with "Retries exceeded, couldn't
reconnect to 127.0.0.1:####". I see this for 4_0 and 4_2 jboss branches, but guess
it's the same with head.
One of the testcases is IiopRemoteUnitTestCase. I've checked
ejb3/src/test/org/jboss/ejb3/test/iiop/unit/IiopRemoteUnitTestCase.java and there is
'props.put("java.naming.provider.url",
"corbaloc::localhost:3528/NameService");'. Instead of localhost there should
be used the node0 property. I guess the others have the same problem.
--
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