[AMQ-3842] test units should run discovery mechanism via loopback device

• Type: Bug
• Status: Closed
• Priority: Trivial
• Resolution: Not A Problem
• Affects Version/s: 5.6.0
• Component/s: Test Cases
• Labels: discovery

Environment

NAT FW

• Regression: Unit Test Broken
• Assignee: Unassigned
• Reporter: Mark
• Created: 15/May/12 22:57
• Updated: 21/May/12 12:55
• Resolved: 21/May/12 12:55

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 (and also produces spam packets on the local network during testing