You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2012/05/21 14:55:41 UTC
[jira] [Closed] (AMQ-3842) test units should run discovery
mechanism via loopback device
[ https://issues.apache.org/jira/browse/AMQ-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish closed AMQ-3842.
-----------------------------
Resolution: Not A Problem
> 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 (and also produces spam packets on the local network during testing :-)
--
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