Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-6515

Log message when stopping listeners doesn't point to port shifted by port offset definition

    XMLWordPrintable

Details

    • Hide

      Start EAP with defined ports offset => either start it in domain and then check log of server-two or start it in standalone with -Djboss.socket.binding.port-offset=101
      Steps for standalone mode:

      1. start server with shifted port offset ./standalone.sh -Djboss.socket.binding.port-offset=101
      2. stop server ./jboss-cli.sh -c --controller=127.0.0.1:10091 ':shutdown'
      3. check the logs for port shown as part of [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 127.0.0.1:$PORT where the port $PORT should be 8181 but is 8080
      Show
      Start EAP with defined ports offset => either start it in domain and then check log of server-two or start it in standalone with -Djboss.socket.binding.port-offset=101 Steps for standalone mode: start server with shifted port offset ./standalone.sh -Djboss.socket.binding.port-offset=101 stop server ./jboss-cli.sh -c --controller=127.0.0.1:10091 ':shutdown' check the logs for port shown as part of [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 127.0.0.1:$PORT where the port $PORT should be 8181 but is 8080

    Description

      When stopping server, the log message for undertow listener being stopped points to port which is not the actual port used in case when the server was started with shifted ports offset.

      Attachments

        Issue Links

          clones

          Bug - A problem which impairs or prevents the functions of the product. JBEAP-4182 Log message when stopping listeners doesn't point to port shifted by port offset definition

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Verified

          Activity

            Public project attachment banner

              context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
              current Project key: WFLY

              People

                sdouglas1@redhat.com Stuart Douglas
                sdouglas1@redhat.com Stuart Douglas
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: