Uploaded image for project: 'Codehaus Cargo'
  1. CARGO-1265

For Existing InstalledLocalContainer, cargo.jboss.management-native.port value incorrectly defaults to 9990 (the http management port)

    Details

    • Type: Bug
    • Status: Closed (View workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Affects versions: 1.4.7
    • Fix versions: 1.4.8
    • Components: JBoss
    • Labels:
      None
    • Environment:

      Windows 7 and RHEL 6.2, Maven 3.0.5, Jboss EAP 6.2.0 (7.3.0.Final-redhat-14)

      Description

      In the constructor for JBoss7xExistingLocalConfiguration, it sets the default native port to 9990:

      setProperty(JBossPropertySet.JBOSS_MANAGEMENT_NATIVE_PORT, "9990");

      This results in command execution similar to:

      "C:\Program Files\Java\jdk1.6.0_34\bin\java.exe" -jar C:\jbosseap2nd\jboss-eap-6.2\jboss-modules.jar -mp C:/jbosseap2nd/jboss-eap-6.2/modules org.jboss.as.cli --connect --controller=localhost:9990 command=:shutdown

      and it won't connect to stop the container.

      Workaround: Explicitly set cargo.jboss.management-native.port to 9999. The use of port offset will properly derive from that value.

        Attachments

          Activity

            People

            • Assignee:
              savasalitokmen Savas Ali Tokmen (Inactive)
              Reporter:
              dougschnee Doug Schnee (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: