Red Hat Bugzilla – Bug 823691
Agent tests use hard-coded port numbers
Last modified: 2013-09-01 06:18:45 EDT
This can cause intermittent test failures due to port conflicts, particularly when two jobs in Jenkins (e.g. rhq-master and rhq-release) run simultaneously on the same slave.
I think we need to either make the ports configurable via sysprops as we did for the comm tests, or add some code that finds a free port in a certain port range and then uses that port. I see the following hard-coded ports in the Agent*Test classes: 11111, 22222, 17777, 18888, 12345, 22345.
Taking this bug since I had started doing some work on it already.
The ports cited in the description have been parameterized. Changes have been pushed to master.
commit hash: fee4a644165
Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.