XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Minor Minor
    • None
    • 12.9.0.GA
    • runtime-detection
    • None
    • 8
    • Hide

      steps:
      1. install a local EAP v7.1.0 binary
      2. On Studio, create a new server, create a new runtime environment to point to the server root folder.
      3. double click the server to see the overview page.
      4. On the port offset under server ports, define a custom offset like 100, see attached
      5. Note that the standalone.xml keeps default, so jboss.socket.binding.port-offset is 0
      6. start the server

      expected result:
      since I manually define a port offset, the server should start with the port, as the web console port as 8180, management port 10090

      actual result:
      the server is still started with default port-offset (0)

      below log:

      11:28:07,130 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
      11:28:07,130 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
      11:28:07,130 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.1.0.GA (WildFly Core 3.0.10.Final-redhat-1) started in 7005ms - Started 430 of 656 services (353 services are lazy, passive or on-demand)

      Show
      steps: 1. install a local EAP v7.1.0 binary 2. On Studio, create a new server, create a new runtime environment to point to the server root folder. 3. double click the server to see the overview page. 4. On the port offset under server ports, define a custom offset like 100, see attached 5. Note that the standalone.xml keeps default, so jboss.socket.binding.port-offset is 0 6. start the server expected result: since I manually define a port offset, the server should start with the port, as the web console port as 8180, management port 10090 actual result: the server is still started with default port-offset (0) below log: 11:28:07,130 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management 11:28:07,130 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 11:28:07,130 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.1.0.GA (WildFly Core 3.0.10.Final-redhat-1) started in 7005ms - Started 430 of 656 services (353 services are lazy, passive or on-demand)
    • NEW

      When testing the local server, I found the port offset checkbox does not work.

        1. port-offset.jpg
          271 kB
          Bin Hu
        2. version.jpg
          64 kB
          Bin Hu

              jmaury@redhat.com Jeff MAURY
              rhn-support-bihu Bin Hu
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: