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

Socket bindings configuration is ignored by installer.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 7.0.0.DR8
    • 7.0.0.DR7
    • Installer
    • None
    • Regression
    • Hide

      On Socket Binding screen choose "Select Offset Type -> +100 offset".
      On Configure runtime environment screen choose to "Perform additional post-install configuration" and check some option (eg Install password vault).
      Finish the installation.

      Show
      On Socket Binding screen choose "Select Offset Type -> +100 offset". On Configure runtime environment screen choose to "Perform additional post-install configuration" and check some option (eg Install password vault). Finish the installation.

    Description

      I am unable to perform any post-install action once I change port-offset during installation. Installation will ends with failure.

      Actual results:

      IzPack variable state written to /home/pkremens/EAP-7.0.0/installation/InstallationLog.txt
      Exit code: 0
      Command completed successfully.
      Starting operation: -genseckey with keystore: /home/pkremens/EAP-7.0.0/vault.keystore
      Operation: -genseckey with keystore: /home/pkremens/EAP-7.0.0/vault.keystore was successful.
      Exit code: 0
      Command completed successfully.
      Unpacking complete.
      JBOSS_HOME adjusted to: /home/pkremens/EAP-7.0.0
      Starting standalone Server using .xml config.
      =========================================================================
      
        JBoss Bootstrap Environment
      
        JBOSS_HOME: /home/pkremens/EAP-7.0.0
      
        JAVA: /usr/lib/java/jdk1.8.0_last/bin/java
      
        JAVA_OPTS:  -server -Xms1303m -Xmx1303m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
      
      =========================================================================
      
      13:09:17,780 INFO  [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final
      13:09:17,937 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
      13:09:17,986 INFO  [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: WildFly Core 2.0.0.Alpha11 "Kenny" starting
      13:09:18,718 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=ExampleDS' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
      13:09:18,749 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
      13:09:18,772 INFO  [org.xnio] (MSC service thread 1-1) XNIO version 3.3.1.Final
      13:09:18,781 INFO  [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.1.Final
      13:09:18,813 INFO  [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.9.Final
      13:09:18,945 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
      13:09:18,946 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0054: Admin console is not enabled
      [ Server code detected: WFLYSRV0025 ]
      Waiting for server to be ready. This could take up to 40 seconds.
      Application Server successfully started.
      Trying to connect to Management Interface...(1/5).
      Trying to connect to Management Interface...(2/5).
      Trying to connect to Management Interface...(3/5).
      Trying to connect to Management Interface...(4/5).
      Trying to connect to Management Interface...(5/5).
      Failed to connect to Management Interface after 5 attempts.
      Trying to connect to Management Interface...(1/5).
      Trying to connect to Management Interface...(2/5).
      Trying to connect to Management Interface...(3/5).
      Trying to connect to Management Interface...(4/5).
      Trying to connect to Management Interface...(5/5).
      Failed to connect to Management Interface after 5 attempts.
      Advanced configuration command failed: /core-service=vault:add(vault-options=[("KEYSTORE_URL" => "${jboss.home.dir}/vault.keystore"), ("KEYSTORE_PASSWORD" => "MASK-3Is8EMlTuqp"), ("KEYSTORE_ALIAS" => "vault"), ("SALT" => "8675309K"), ("ITERATION_COUNT" => "44"), ("ENC_FILE_DIR" => "${jboss.home.dir}/vault")])
      {
          "outcome" => "failed",
          "failure-description" => "No ModelControllerClient was available to execute the request.",
          "command" => "/core-service=vault:add(vault-options=[(\"KEYSTORE_URL\" => \"${jboss.home.dir}/vault.keystore\"), (\"KEYSTORE_PASSWORD\" => \"MASK-3Is8EMlTuqp\"), (\"KEYSTORE_ALIAS\" => \"vault\"), (\"SALT\" => \"8675309K\"), (\"ITERATION_COUNT\" => \"44\"), (\"ENC_FILE_DIR\" => \"${jboss.home.dir}/vault\")])"
      }
      Running on-fail server check.
      Shutting server down.
      Trying to connect to Management Interface...(1/5).
      Trying to connect to Management Interface...(2/5).
      Trying to connect to Management Interface...(3/5).
      Trying to connect to Management Interface...(4/5).
      Trying to connect to Management Interface...(5/5).
      Failed to connect to Management Interface after 5 attempts.
      {"outcome" => "failed","failure-description" => "No ModelControllerClient was available to execute the request.","command" => ":shutdown"}
      

      Expected results:
      Post-install action is performed without any failure

      Same issue seen on EAP6 in past - https://bugzilla.redhat.com/show_bug.cgi?id=1009421

      Attachments

        Activity

          People

            spyrkob Bartosz Spyrko-Smietanko
            pkremens@redhat.com Petr Kremensky (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: