[
https://jira.jboss.org/jira/browse/EJBTHREE-880?page=com.atlassian.jira.p...
]
Brian Stansberry commented on EJBTHREE-880:
-------------------------------------------
Perhaps the solution here is to be more careful in how we use the "node0" ant
property. If the set of tests requires localhost, the server should be bound to
"localhost" not to a variable "node0" and the test driver should be
told the server is bound to localhost, not "node0". This leaves node0 available
as a variable for those test targets that need it.
BTW, the issue here isn't just a requirement to add a multicast route. On Windows you
cannot run clustering tests if node0 = localhost and node1 = eth0. It just won't work.
Well, at least not with XP and earlier, haven't tried later. :-) This means community
members who want to work on EJB3 and use Windows machines cannot run the EJB3 testsuite.
(Personal aside: 5 years ago I was such a person, except working on AS. If I hadn't
been able to run the AS testsuite on my machine I would not have become an active
contributor.)
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