Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-3050

Can't search for connectors, type=ThreadPool MBeans when starting JBoss with -b hostname

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Out of Date
    • Affects Version/s: 4.3.0.GA_CP06
    • Fix Version/s: TBD EAP 4
    • Component/s: Other
    • Labels:
      None
    • Environment:

      Red Hat Enterprise Linux Server 5.4, Sun JDK 1.6.0_11, JBoss EAP 4.3 CP06

    • Affects:
      Release Notes
    • Release Notes Text:
      Hide
      <para>
      When JBoss Enterprise Application Platform is started with the <literal>-b &lt;hostname&gt;</literal> flag, filtering by <literal>jboss.web:name=ajp-&lt;hostname&gt;/&lt;ip_address&gt;-8009,type=ThreadPool,*</literal> returns no results. This makes it impossible to use SNMP to export data to other monitoring tools because the configuration in <filename>deploy/snmp-adapter.sar/attributes.xml</filename> cannot find the bean.

      </para><para>It is worth noting that while the following definition does not work:
      </para><para><programlisting>&lt;mbean name=&quot;jboss.web:name=ajp-&lt;hostname&gt;/&lt;ip_address&gt;-8009,type=ThreadPool&quot; oid-prefix=&quot;.1.2.3.4.1&quot;&gt;</programlisting>

      </para><para>The following definition does work as expected:
      </para><para><programlisting>&lt;mbean name=&quot;jboss.web:name=ajp-&lt;ip_address&gt;-8009,type=ThreadPool&quot; oid-prefix=&quot;.1.2.3.4.1&quot;&gt;</programlisting>
      </para>
      Show
      <para> When JBoss Enterprise Application Platform is started with the <literal>-b &lt;hostname&gt;</literal> flag, filtering by <literal>jboss.web:name=ajp-&lt;hostname&gt;/&lt;ip_address&gt;-8009,type=ThreadPool,*</literal> returns no results. This makes it impossible to use SNMP to export data to other monitoring tools because the configuration in <filename>deploy/snmp-adapter.sar/attributes.xml</filename> cannot find the bean. </para><para>It is worth noting that while the following definition does not work: </para><para><programlisting>&lt;mbean name=&quot;jboss.web:name=ajp-&lt;hostname&gt;/&lt;ip_address&gt;-8009,type=ThreadPool&quot; oid-prefix=&quot;.1.2.3.4.1&quot;&gt;</programlisting> </para><para>The following definition does work as expected: </para><para><programlisting>&lt;mbean name=&quot;jboss.web:name=ajp-&lt;ip_address&gt;-8009,type=ThreadPool&quot; oid-prefix=&quot;.1.2.3.4.1&quot;&gt;</programlisting> </para>
    • Release Notes Docs Status:
      Not Required

      Description

      When starting JBoss with -b <ip>, the thread pool MBean is:

      jboss.web:name=ajp-<ip_address>-8009,type=ThreadPool

      So, when filtering by "jboss.web:name=ajp-<ip_address>-8009,type=ThreadPool,*" it works fine and returns the MBean.

      But when starting JBoss with -b <hostname>, the MBean looks like this:

      name=ajp-<hostname>/<ip_address>-8009,type=ThreadPool

      And, when filtering by "jboss.web:name=ajp-<hostname>/<ip_address>-8009,type=ThreadPool,*" there are no results. I haven't found a filter that returns this MBean.

      This makes impossible to use SNMP to export data to another monitoring tool, as the configuration in deploy/snmp-adapter.sar/attributes.xml can't find the MBean. For instance, if I define
      <mbean name="jboss.web:name=ajp-<hostname>/<ip_address>-8009,type=ThreadPool" oid-prefix=".1.2.3.4.1">

      It does not work, but if I define it like
      <mbean name="jboss.web:name=ajp-<ip_address>-8009,type=ThreadPool" oid-prefix=".1.2.3.4.1">
      it works.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  dimitris Dimitrios Andreadis
                  Reporter:
                  pbravoco Pilar Bravo Contreras
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: