[arquillian-issues] [JBoss JIRA] (ARQ-660) Automatically pick an open port: embedded and managed containers should be configurable to automatically pick another open port if their default port is closed, instead of failing all tests with "Could not deploy to container"

[Geoffrey De Smet (Created) (JIRA)]

Automatically pick an open port: embedded and managed containers should be configurable to automatically pick another open port if their default port is closed, instead of failing all tests with "Could not deploy to container"
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: ARQ-660
                 URL: https://issues.jboss.org/browse/ARQ-660
             Project: Arquillian
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Configuration
    Affects Versions: 1.0.0.CR5
            Reporter: Geoffrey De Smet
            Priority: Critical
             Fix For: 1.1.0.Beta1


When running our tests on hudson/jenkins, we don't know which hudson slave will run our job (any slave marked as AnyRHEL6 can run it) and we don't know what other jobs will be running at the same time.
It's impossible to guess which port will be free because:
- the server might have some services set up on some ports
- the other hudson jobs might be using the same ports
- the other hudson jobs might be a release or topic branch of our own project and will be using the same ports

If an embedded or managed container starts and tries to take a non-open port, it crashes and all the tests fail.
**So all our arquillian tests randomly fail.**

The arquillian.xml configuration should support configuring a port to something like
"any open port in the range 8000-8999". If our test cases properly use "@ArquillianResource URL baseURL" (which they do), that shouldn't be a problem.
Next, the container implements, gradually one by one, should support this (or throw an UnsupportOperationException if they don't support it yet).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira