Description of problem:

When the modcluster subsystem is unable to connect to a proxy, the jboss-cli commands :read-proxies-configuration and :read-proxies-info fail with an unhelpful error.

On both the domain controller and application host, :read-proxies-info and :read-proxies-configuration fail with the same error. This is the output from the application host:

[domain@localhost:9999 subsystem=modcluster] pwd
/host=localhost/server=cluster2/subsystem=modcluster

[domain@localhost:9999 subsystem=modcluster] :list-proxies
{
    "outcome" => "success",
    "result" => [
        "web02:8009",
        "web01:8009"
    ]
}

[domain@localhost:9999 subsystem=modcluster] :read-proxies-configuration
{
    "outcome" => "failed",
    "result" => undefined,
    "failure-description" => "JBAS014749: Operation handler failed: newValue is null",
    "rolled-back" => true
}

[domain@localhost:9999 subsystem=modcluster] :read-proxies-info
{
    "outcome" => "failed",
    "result" => undefined,
    "failure-description" => "JBAS014749: Operation handler failed: newValue is null",
    "rolled-back" => true
}


Version-Release number of selected component (if applicable):


How reproducible:

Always


Steps to Reproduce:
1. Set modcluster's proxy-list
2. Don't run httpd on that specified proxy-list ip/port
3. Attempt a :read-proxies-configuration or :read-proxies-info command

Actual results:

The CLI commands fail if an httpd is down


Expected results:

The CLI command works if an httpd is down