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

[GSS](7.0.z) Undertow listener start/stop messages do not reflect jboss.socket.binding.port-offset

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Minor
    • 7.0.6.CR1, 7.0.6.GA
    • 7.0.4.GA
    • Undertow
    • None
    • EAP 7.0.6

    Description

      Start JBoss with a jboss.socket.binding.port-offset. The http start message is correct, but ajp is incorrect:

      2017-02-14 10:21:17,251 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow AJP listener ajp listening on 127.0.0.1:8009
      2017-02-14 10:21:17,251 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8180

      Then both stop messages are incorrect:

      2017-02-14 10:21:31,004 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0007: Undertow AJP listener ajp stopped, was bound to 127.0.0.1:8009
      2017-02-14 10:21:31,004 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 127.0.0.1:8080

      Attachments

        Issue Links

          Activity

            People

              rhn-support-iweiss Ingo Weiss
              rhn-support-aogburn Aaron Ogburn
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: