All application returns "404 Not Found" when wrong "proxies" setting is specified to modcluster subsystem in EAP 7.1

Issue

We can not access any application ("404 Not Found" is returned) when a wrong value is specified to the proxies setting to <mod-cluster-config> in the modcluster subsystem in EAP 7.1.x:

        <subsystem xmlns="urn:jboss:domain:modcluster:3.0">
            <mod-cluster-config proxies="proxy1 proxy2" advertise="false" connector="default">
                <dynamic-load-provider>
                    <load-metric type="cpu"/>
                </dynamic-load-provider>
            </mod-cluster-config>
        </subsystem>

    ...(snip)...

    <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
        ...
        <outbound-socket-binding name="proxy1">
            <remote-destination host="192.0.2.10" port="6666"/>
        </outbound-socket-binding>
        <!-- proxy2 is not defined!! -->
    </socket-binding-group>

There's no other ERROR message than the following on the server start-up:

ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: JBoss EAP 7.1.5.GA (WildFly Core 3.0.19.Final-redhat-00001) started (with errors) in 9050ms - Started 474 of 726 services (4 services failed or missing dependencies, 428 services are lazy, passive or on-demand)

When we tried to deploy an application, the following ERROR was logged:

ERROR [org.jboss.as.server] (ServerService Thread Pool -- 74) WFLYSRV0021: Deploy of deployment "test.war" was rolled back with the following failure message: undefined