[jboss-jira] [JBoss JIRA] (WFCORE-4581) Defining management-interface with https-only socket-bindings causes server to shut down instantly
Jeff Mesnil (Jira)
issues at jboss.org
Thu Jul 25 12:01:00 EDT 2019
[ https://issues.jboss.org/browse/WFCORE-4581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Mesnil reassigned WFCORE-4581:
-----------------------------------
Assignee: Richard Opalka (was: Jeff Mesnil)
> Defining management-interface with https-only socket-bindings causes server to shut down instantly
> --------------------------------------------------------------------------------------------------
>
> Key: WFCORE-4581
> URL: https://issues.jboss.org/browse/WFCORE-4581
> Project: WildFly Core
> Issue Type: Bug
> Reporter: Bartosz Spyrko
> Assignee: Richard Opalka
> Priority: Major
>
> management interface is configured to support only https connections:
> {noformat}
> <management-interfaces>
> <http-interface security-realm="ManagementRealm">
> <http-upgrade enabled="true"/>
> <socket-binding https="management-https"/>
> </http-interface>
> </management-interfaces>
> {noformat}
> On startup the server will not report any errors, but will immediately shutdown:
> {noformat}
> $ ./bin/standalone.sh
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /Users/spyrkob/workspaces/set/tools/installer/wildfly-core/build/target/wildfly-core-9.0.0.Beta4-SNAPSHOT
> JAVA: /Library/Java/JavaVirtualMachines/jdk1.8.0_152.jdk/Contents/Home/bin/java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> 16:45:34,016 INFO [org.jboss.modules] (main) JBoss Modules version 1.9.1.Final
> 16:45:34,483 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.5.Final
> 16:45:34,496 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
> 16:45:34,660 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Core 9.0.0.Beta4-SNAPSHOT starting
> 16:45:35,383 INFO [org.wildfly.security] (ServerService Thread Pool -- 6) ELY00001: WildFly Elytron version 1.9.0.CR4
> 16:45:35,536 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 16:45:35,569 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0040: Creating http management service using secure-socket-binding (management-https)
> 16:45:35,592 INFO [org.xnio] (MSC service thread 1-6) XNIO version 3.7.1.Final
> 16:45:35,600 INFO [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.7.1.Final
> 16:45:35,672 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 5.0.9.Final
> 16:45:35,694 INFO [org.jboss.as.patching] (MSC service thread 1-7) WFLYPAT0050: WildFly cumulative patch ID is: base, one-off patches include: none
> 16:45:35,715 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-7) WFLYDM0111: Keystore /Users/spyrkob/workspaces/set/tools/installer/wildfly-core/build/target/wildfly-core-9.0.0.Beta4-SNAPSHOT/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
> 16:45:35,896 WARN [org.jboss.as.domain.http.api.undertow] (MSC service thread 1-7) WFLYDMHTTP0003: Unable to load console module for slot main, disabling console
> 16:45:35,982 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 16:45:35,988 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0050: WildFly Core 9.0.0.Beta4-SNAPSHOT stopped in 2ms
> {noformat}
> In previous release this was a valid settings, the problem seems to have been introduced by WFCORE-4442
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
More information about the jboss-jira
mailing list