Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-5111

(7.1.0) :read-proxies-configuration and :read-proxies-info fail when at least one of the proxies is unreachable

    XMLWordPrintable

Details

    Description

      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
      }
      

      In the above example, modcluster was not able to connect to the proxies due to an ssl misconfiguration in the modcluster subsystem in domain.xml.

      Attachments

        Issue Links

          Activity

            People

              rhn-support-aogburn Aaron Ogburn
              rhn-support-aogburn Aaron Ogburn
              Michal Karm Michal Karm
              Michal Karm Michal Karm
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: