2 Replies Latest reply on Jun 28, 2013 12:44 PM by Kristina Clair

    :read-proxies-info and :read-proxies-configuration fail in domain mode

    Kristina Clair Newbie

      We're running EAP 6.1.0 and mod_cluster 1.2.4Final on RHEL 6.

       

      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

      }

      [domain@localhost:9999 subsystem=modcluster]