Uploaded image for project: 'mod_cluster'
  1. mod_cluster
  2. MODCLUSTER-91

Connector bind address of 0.0.0.0 propagated to proxy

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 1.0.1.GA
    • Fix Version/s: 1.1.0.Beta1
    • Component/s: None
    • Labels:
      None

      Description

      Marek Goldmann wrote:
      > I'm encountered a strange error. When I bind JBoss instance to 0.0.0.0
      > address instead of a fixed ethernet address, node gets registered in
      > mod_cluster, shows in mod_cluster-manager, but every request to
      > registered contexts throws 503 error.
      >
      > httpd error log:
      >
      > [Fri Aug 07 03:21:05 2009] [error] (111)Connection refused: proxy:
      > ajp: attempt to connect to 0.0.0.0:8009 (0.0.0.0) failed
      > [Fri Aug 07 03:21:05 2009] [error] ap_proxy_connect_backend disabling
      > worker for (0.0.0.0)
      > [Fri Aug 07 03:21:15 2009] [error] proxy: ajp: disabled connection for
      > (0.0.0.0)
      > [Fri Aug 07 03:21:25 2009] [error] proxy: ajp: disabled connection for
      > (0.0.0.0)
      >
      > This looks like a bug for me, because many administrators are binding
      > JBoss to 0.0.0.0.

      The java side needs to understand that 0.0.0.0 is useless as a client address and send something useful. Trick is deciding what's useful.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  pferraro Paul Ferraro
                  Reporter:
                  brian.stansberry Brian Stansberry
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  8 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: