mod_cluster fails to start with negative port offset ---------------------------------------------------- Key: WFLY-9343 URL: https://issues.jboss.org/browse/WFLY-9343 Project: WildFly Issue Type: Bug Components: mod_cluster Affects Versions: 11.0.0.CR1 Reporter: Radoslav Husar Assignee: Radoslav Husar Priority: Critical When using a negative port-offset in HA profiles, mod-cluster fails to start. This problem doesn't occur in non-HA profiles (e.g. default), because the modcluster subsystem is not present in them. Server log contains: {noformat} 19:59:41,337 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service org.wildfly.mod_cluster.config: org.jboss.msc.service.StartException in service org.wildfly.mod_cluster.config: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1978) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.IllegalArgumentException: port out of range:-100 at java.net.InetSocketAddress.checkPort(InetSocketAddress.java:143) at java.net.InetSocketAddress.<init>(InetSocketAddress.java:188) at org.jboss.as.network.SocketBinding.getSocketAddress(SocketBinding.java:129) at org.wildfly.extension.mod_cluster.ModClusterConfigurationServiceBuilder.getValue(ModClusterConfigurationServiceBuilder.java:272) at org.wildfly.extension.mod_cluster.ModClusterConfigurationServiceBuilder.getValue(ModClusterConfigurationServiceBuilder.java:104) at org.jboss.msc.service.ValueService.start(ValueService.java:49) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) ... 3 more 19:59:41,492 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 16 (per class), which is derived from the number of CPUs on this host. 19:59:41,493 INFO [org.jboss.as.ejb3] (MSC service thread 1-5) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing. 19:59:41,657 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 65) WFLYUT0014: Creating file handler for path '/home/kwart/test/710CR1/jboss-eap-7.1/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]'] 19:59:41,663 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0012: Started server default-server. 19:59:41,666 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting 19:59:41,729 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) WFLYEJB0493: EJB subsystem suspension complete 19:59:41,747 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0006: Undertow AJP listener ajp listening on 127.0.0.1:7909 19:59:41,749 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:7980 19:59:41,881 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] 19:59:41,989 INFO [org.jboss.as.patching] (MSC service thread 1-3) WFLYPAT0050: JBoss EAP cumulative patch ID is: base, one-off patches include: none 19:59:42,006 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-3) WFLYDM0111: Keystore /home/kwart/test/710CR1/jboss-eap-7.1/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost 19:59:42,043 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) WFLYDS0013: Started FileSystemDeploymentService for directory /home/kwart/test/710CR1/jboss-eap-7.1/standalone/deployments 19:59:42,151 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8343 19:59:42,252 INFO [org.jboss.ws.common.management] (MSC service thread 1-7) JBWS022052: Starting JBossWS 5.1.9.Final-redhat-1 (Apache CXF 3.1.12.redhat-1) 19:59:42,259 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "modcluster")]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.mod_cluster.config" => "Failed to start service Caused by: java.lang.IllegalArgumentException: port out of range:-100"}} 19:59:42,282 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report WFLYCTL0186: Services which failed to start: service org.wildfly.mod_cluster.config: Failed to start service 19:59:42,367 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server 19:59:42,369 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9890/management 19:59:42,370 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9890 19:59:42,370 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: JBoss EAP 7.1.0.GA (WildFly Core 3.0.1.Final-redhat-1) started (with errors) in 4175ms - Started 309 of 642 services (3 services failed or missing dependencies, 421 services are lazy, passive or on-demand) {noformat}