[
https://jira.jboss.org/jira/browse/EJBTHREE-880?page=com.atlassian.jira.p...
]
Brian Stansberry commented on EJBTHREE-880:
-------------------------------------------
If you need to set "jgroups.udp.mcast_addr" something is broken. What testsuite
is it that you are running that requires this?
It should be simple to implement Alex's suggestion of having the multicast sockets
both listen for multicasxt on node1's interface. At least with the trunk version of
the ejb3 testsuite build-test.xml, you can pass -Dnode0.jgroups.bind_addr=xxx and
-Dnode1.jgroups.bind_addr=xxx and you'll get the effect.
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