Details

    • Sub-task
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Done
    • EAP_EWP 5.1.2
    • EAP_EWP 5.2.0
    • HornetQ
    • None
    • Release Notes
    • 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.
    • Documented as Resolved Issue
    • NEW

    Attachments

      Activity

        People

          rhn-support-jbertram Justin Bertram
          rhn-support-jbertram Justin Bertram
          Scott Thomas Scott Thomas (Inactive)
          Votes:
          0 Vote for this issue
          Watchers:
          3 Start watching this issue

          Dates

            Created:
            Updated:
            Resolved: