Details

    • Type: Sub-task
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: EAP_EWP 5.1.2
    • Fix Version/s: EAP_EWP 5.2.0
    • Component/s: HornetQ
    • Labels:
      None
    • Affects:
      Release Notes
    • Release Notes Text:
      Hide
       In previous versions of JBoss Enterprise Application Platform 5, when a HornetQ "connector" was bound to <literal>0.0.0.0</literal> HornetQ would tell a remote client to connect to the same address. However, <literal>0.0.0.0</literal> is meaningless to a remote client. This issue was resolved by detecting the <literal>0.0.0.0</literal> binding and replacing that value with the result of <code>InetAddress.getLocalHost().getHostName()</code> so that the remote client can connect properly.
      Show
       In previous versions of JBoss Enterprise Application Platform 5, when a HornetQ "connector" was bound to <literal>0.0.0.0</literal> HornetQ would tell a remote client to connect to the same address. However, <literal>0.0.0.0</literal> is meaningless to a remote client. This issue was resolved by detecting the <literal>0.0.0.0</literal> binding and replacing that value with the result of <code>InetAddress.getLocalHost().getHostName()</code> so that the remote client can connect properly.
    • Release Notes Docs Status:
      Documented as Resolved Issue
    • Docs QE Status:
      NEW

      Gliffy Diagrams

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jbertram Justin Bertram
                Reporter:
                jbertram Justin Bertram
                Writer:
                Scott Thomas
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: