modcluster:read-proxies-configuration throws IllegalArgumentException

Environment

• JBoss Enterprise Application Platform (EAP) 6.x
• mod_cluster

Issue

• In some cases, the modcluster:read-proxies-configuration CLI command throws an IllegalArgumentException:

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

Resolution

• Ensure JBoss is connected to all proxies in its proxy-list

Root Cause

• One of the configured proxies in the mod-cluster proxy-list is not running and JBoss is not connected to it.
• Content from issues.jboss.org is not included.WFLY-6680
• Content from issues.jboss.org is not included.JBEAP-5111
• This content is not included.BZ-1343633

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.