[jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-880) Hard-coded localhost in ejb3 test suite

[Juraci Paixao Krohling (JIRA)]

    [ https://jira.jboss.org/jira/browse/EJBTHREE-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12454224#action_12454224 ] 

Juraci Paixao Krohling commented on EJBTHREE-880:
-------------------------------------------------

I tried different setups locally. I'm by no means an expert in clustering/network configuration, so, maybe you can give a try to get a working environment in some Hudson/QA machine, using lo/eth0 as node0/node1? 

I don't really like the idea of having some specific configuration on some machines just for EJB3, but after talking to EJB3 guys, it is pretty clear to me that there are some valid *test cases*. As I said, there is one which checks the consistency of hostname and IP address. The only pair of hostname/ip known for sure is localhost/127.0.0.1.  

> Interesting, so how should these features would work for a customer where the multicast path generally doesn't point to localhost? 

We are talking about tests, right? I suppose that customers have a network setup specially configured to the clustering of their JBoss test instances, so they don't affect SIT/UAT/Production instances. That's basically what I'm looking for here. Isolated environment, to test everything related to EJB3 in a regular basis, without the need to take some machine(s) down or manually configure on every run.

> As well by multicasting, one is allowed to bind to specific interfaces. So in case you really, really need to have everything on localhost (what I still can't understand why), then by these tests you can specifically listen on lo and send through lo. 

If we have two interfaces, lo and eth0, with one JBoss instance in each, multi-casting will still be affected by other JBoss instances accessible through eth0. In some tests, I noticed that some external instances were able to join the cluster whose master was on eth0, but lo was denied to join the cluster. So, even if they are on the same machine, lo is not in the same group as eth0, causing failures. 

> The whole purpose of having node0 and node1 is defeated btw. Why use them when we still rely on localhost? Can't you use separate port sets to run your servers?

No, it is not. We are talking about only EJB3 here, not the entire JBoss AS test suite. So, node0 and node1 are still being used in other parts. 

If you still have doubts about it, please join us at #ejb3


> 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