Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Won't Fix or Usage Issue
    • Affects Version/s: 2.0.0-M1
    • Fix Version/s: None
    • Component/s: Core: Configuration
    • Labels:
      None
    • User impact:
      Low
    • Similar Issues:

      Description

      Sometimes tests seem to fail due to port conflicts. We could avoid this by making port numbers auto-increment. One way to implement this would be to use a variable like "$

      {MULE_SEQUENTIAL_PORT}

      " in the config and then implement a custom property placeholder handler.

      If this were used to set global endpoints in the config these could then be accessed from the Java test code (the test would send to the global name and have no need to know the port number).

      We could extend the test framework to restart tests a second time on error. If the port number were taken from a global (thread safe) counter we would get new ports for each test.

        Attachments

          Activity

            People

            • Assignee:
              andrew Andrew Perepelytsya
              Reporter:
              acooke Andrew Cooke
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: