[QPIDJMS-76] multicast discovery tests fail sporadically on some of the Jenkins CI nodes

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Done
• Affects Version/s: 0.4.0
• Component/s: qpid-jms-discovery
• Assignee: Robbie Gemmell
• Reporter: Robbie Gemmell
• Created: 23/Jun/15 10:01
• Updated: 06/Jan/16 12:32
• Resolved: 24/Jun/15 14:12

Description

The multicast discovery tests fail to work on some of the Jenkins 'Ubuntu' label nodes, but succeed on others.

The tests have a pre-run JUnit assumption validation that verifies multicast is operational, and skips the test if is not in order to avoid failing on systems with firewalls etc. This verification is succeeding which allows the tests run, but they then fail as the running ActiveMQ broker doesn't get discovered and the connection attempt fails after exhausting its retry limit. The assumption verification either needs updating, or the tests configured differently, to make the tests pass or skip if they can't be run successfully in the particular nodes environment.

Issue Links

• is related to: QPIDJMS-77 update selection of default multicast discovery interface for consistency, and include trace logging of the process