Details

    • Type: Bug
    • Status: Closed (View workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects versions: 1.4.18
    • Fix versions: 1.4.19
    • Components: WebSphere
    • Labels:
      None

      Description

      If maven build using Cargo WebSphere fails while running tests, WebSphere isn't stopped because it runs in separate process.

      Repeated Cargo run will then fail as WebSphere port is already in use by already running WebSphere instance.

      Solution would be to ensure the WebSphere server is stopped - Just like all other containers (which do not create a separate JVM, so are directly by Cargo's standard features).

        Attachments

          Activity

            People

            • Assignee:
              ksuta Karel Suta
              Reporter:
              ksuta Karel Suta
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: