Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Fri, 18 May 2012 21:49:08 +0000 (UTC)
From: "Mark (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <1605906718.16604.1337377748388.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <506350834.1785.1337122746809.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (AMQ-3842) test units should run discovery
 mechanism via loopback device
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMQ-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark updated AMQ-3842:
----------------------

    Description: 
Many test units are failing on boxes with NAT firewalls enabled, although discovery via loopback device would (IMHO) be sufficient for test units.

My NAT setup allows all traffic via lo, but only related traffic via eth0 etc., which should be the regular fw security setup on most or many end-user boxes.

The test org.apache.activemq.transport.discovery.DiscoveryTransportNoBrokerTest (for example) makes activemq send out discovery messages via eth0, which is probably not a perfect solution if one wants to have portable test units.

  was:Many test units are failing on boxes with NAT firewalls enabled, although discovery via loopback device would (IMHO) be sufficient for test units.

    
> test units should run discovery mechanism via loopback device
> -------------------------------------------------------------
>
>                 Key: AMQ-3842
>                 URL: https://issues.apache.org/jira/browse/AMQ-3842
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Test Cases
>    Affects Versions: 5.6.0
>         Environment: NAT FW
>            Reporter: Mark
>            Priority: Trivial
>              Labels: discovery
>
> Many test units are failing on boxes with NAT firewalls enabled, although discovery via loopback device would (IMHO) be sufficient for test units.
> My NAT setup allows all traffic via lo, but only related traffic via eth0 etc., which should be the regular fw security setup on most or many end-user boxes.
> The test org.apache.activemq.transport.discovery.DiscoveryTransportNoBrokerTest (for example) makes activemq send out discovery messages via eth0, which is probably not a perfect solution if one wants to have portable test units.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira