qpid-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From conflue...@apache.org
Subject [CONF] Apache Qpid > Qpid JMX Management Console FAQ
Date Thu, 03 Sep 2009 10:38:08 GMT
    <base href="http://cwiki.apache.org/confluence">
            <link rel="stylesheet" href="/confluence/s/1519/1/1/_/styles/combined.css?spaceKey=qpid&amp;forWysiwyg=true"
<body style="background-color: white" bgcolor="white">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
     <h2><a href="http://cwiki.apache.org/confluence/display/qpid/Qpid+JMX+Management+Console+FAQ">Qpid
JMX Management Console FAQ</a></h2>
     <h4>Page <b>edited</b> by             <a href="http://cwiki.apache.org/confluence/display/~robbie">Robbie
     <div class="notificationGreySide">

<h2><a name="QpidJMXManagementConsoleFAQ-Errors"></a>Errors</h2>

<h3><a name="QpidJMXManagementConsoleFAQ-HowdoIconnectthemanagementconsoletomybrokerusingsecurity%3F"></a><span
id='tgl_content_qManagementConsoleSecurity' class='cloakToggle'></span> How do I
connect the management console to my broker using security ?</h3>
<span id='content_qManagementConsoleSecurity' class='cloak' style='display: none'>

<p>The <a href="/confluence/display/qpid/Management+Console+Security" title="Management
Console Security">Management Console Security</a> page will give you the instructions
that you should use to set this up.</p>

<h3><a name="QpidJMXManagementConsoleFAQ-IamunabletoconnectQpidJMXMC%2FJConsoletoaremotebrokerrunningonLinux%2Cbutconnectingtolocalhostonthatmachineworks%3F"></a><span
id='tgl_content_rmiServerHostname' class='cloakToggle'></span> I am unable to connect
Qpid JMX MC/JConsole to a remote broker running on Linux, but connecting to localhost on that
machine works ?</h3>
<span id='content_rmiServerHostname' class='cloak' style='display: none'>

<p>The RMI based JMX ConnectorServer used by the broker requries two ports to operate.
The console connects to an RMI Registry running on the primary (default 8999) port and retrieves
the information actually needed to connect to the JMX Server. This information embeds the
hostname of the remote machine, and if this is incorrect or unreachable by the connecting
client the connection will fail.</p>

<p>This situation arises due to the hostname configuration on Linux and is generally
encountered when the remote machine does not have a DNS hostname entry on the local network,
causing the hostname command to return a loopback IP instead of a fully qualified domain name
or IP address accessible by remote client machines. It is described in further detail at:
<a href="http://java.sun.com/javase/6/docs/technotes/guides/management/faq.html#linux1"

<p>To remedy this issue you can set the <em>java.rmi.server.hostname</em>
system property to control the hostname/ip reported to the RMI runtime when advertising the
JMX ConnectorServer. This can also be used to dictate the address returned on a computer with
multiple network interfaces to control reachability. To do so, add the value <em>-Djava.rmi.server.hostname=&lt;desired
hostname/ip&gt;</em> to the QPID_OPTS environment variable before starting the <em>qpid-server</em>

     <div id="commentsSection" class="wiki-content pageSection">
       <div style="float: right;">
            <a href="http://cwiki.apache.org/confluence/users/viewnotifications.action"
class="grey">Change Notification Preferences</a>

       <a href="http://cwiki.apache.org/confluence/display/qpid/Qpid+JMX+Management+Console+FAQ">View
       <a href="http://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=60677&revisedVersion=5&originalVersion=4">View
       <a href="http://cwiki.apache.org/confluence/display/qpid/Qpid+JMX+Management+Console+FAQ?showComments=true&amp;showCommentArea=true#addcomment">Add

Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:commits-subscribe@qpid.apache.org

View raw message