activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-3842) test units should run discovery mechanism via loopback device
Date Fri, 18 May 2012 22:07:06 GMT

    [ https://issues.apache.org/jira/browse/AMQ-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279248#comment-13279248
] 

Timothy Bish commented on AMQ-3842:
-----------------------------------

The tests aren't really designed to be portable, they are designed to test the various use
cases of the Broker.  You may need to make accommodations on your specific machine to allow
all tests to run.  I've added autofail to the test case you mentioned which should prevent
the hang, it will still fail of course. 
                
> 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

        

Mime
View raw message