Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-4182

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

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • 7.1.0.DR2
    • 7.0.0.CR1
    • Undertow
    • None
    • DR2
    • 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

      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.

              sdouglas1@redhat.com Stuart Douglas (Inactive)
              rhatlapa@redhat.com Radim Hatlapatka (Inactive)
              Jan Stourac Jan Stourac
              Jan Stourac Jan Stourac
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - 30 minutes
                  30m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 30 minutes
                  30m