<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 08:52:45 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>MongoDB Jira</title>
    <link>https://jira.mongodb.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.7.1</version>
        <build-number>970001</build-number>
        <build-date>13-04-2023</build-date>
    </build-info>


<item>
            <title>[JAVA-641] JMX registration error</title>
                <link>https://jira.mongodb.org/browse/JAVA-641</link>
                <project id="10006" key="JAVA">Java Driver</project>
                    <description>&lt;p&gt;We are seeing the following error message in our Webserver (resin) log since we are using java driver 2.9.0:&lt;/p&gt;
&lt;p/&gt;
&lt;div id=&quot;syntaxplugin&quot; class=&quot;syntaxplugin&quot; style=&quot;border: 1px dashed #bbb; border-radius: 5px !important; overflow: auto; max-height: 30em;&quot;&gt;
&lt;table cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; border=&quot;0&quot; width=&quot;100%&quot; style=&quot;font-size: 1em; line-height: 1.4em !important; font-weight: normal; font-style: normal; color: black;&quot;&gt;
		&lt;tbody &gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;  margin-top: 10px;   margin-bottom: 10px;  width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;[12-09-11 11:40:21.358] {main} jmx registration error: com.mongodb.util.management.JMException: javax.management.NotCompliantMBeanException: com.mongodb:type=ConnectionPool,host=sx177.ipx/172.x.x.x,port=27018,instance=1 mbean has no MBean interface for class com.mongodb.DBPortPool continuing... &lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
			&lt;/tbody&gt;
&lt;/table&gt;
&lt;/div&gt;
&lt;p/&gt;
&lt;p&gt;This error does not occur using java driver v2.7.3.&lt;/p&gt;

&lt;p&gt;I found out that v2.7.3 uses SimplePool implementing DynamicMBean which v2.9.0 does not. &lt;br/&gt;
The problem is that resin (v4.0.30) checks wether the MBean is an instance of DynamicBean OR implements a MBeanInterface. The class name of the latter must end with the name of the implemented interface or superclass appended with MBean or MXBean.&lt;br/&gt;
The first is the case for v2.7.3 since SimplePool implements DynamicMBean. For v2.9.0 however, neither the first nor the latter is the case because it does not implement DynamicMBean anymore and the implemented interface com.mongodb.MongoConnectionPoolMXBean does not follow the naming convention. The interface name should end with DBPortPoolMBean or DBPortPoolMXBean or SimplePoolMBean or SimplePoolMXBean.&lt;/p&gt;</description>
                <environment>linux 64 bit</environment>
        <key id="50341">JAVA-641</key>
            <summary>JMX registration error</summary>
                <type id="1" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14703&amp;avatarType=issuetype">Bug</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</priority>
                        <status id="6" iconUrl="https://jira.mongodb.org/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="9">Done</resolution>
                                        <assignee username="jeff.yemin@mongodb.com">Jeffrey Yemin</assignee>
                                    <reporter username="kay.agahd@idealo.de">Kay Agahd</reporter>
                        <labels>
                    </labels>
                <created>Wed, 12 Sep 2012 15:53:27 +0000</created>
                <updated>Tue, 19 Mar 2013 14:48:29 +0000</updated>
                            <resolved>Tue, 5 Mar 2013 18:40:15 +0000</resolved>
                                    <version>2.9.0</version>
                                    <fixVersion>2.9.2</fixVersion>
                    <fixVersion>2.11.0</fixVersion>
                                    <component>Monitoring</component>
                                        <votes>0</votes>
                                    <watches>5</watches>
                                                                                                                <comments>
                            <comment id="234364" author="auto" created="Tue, 8 Jan 2013 19:13:52 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;date&apos;: u&apos;2012-10-22T18:29:10Z&apos;, u&apos;email&apos;: u&apos;jeff.yemin@10gen.com&apos;, u&apos;name&apos;: u&apos;Jeff Yemin&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/JAVA-641&quot; title=&quot;JMX registration error&quot; class=&quot;issue-link&quot; data-issue-key=&quot;JAVA-641&quot;&gt;&lt;del&gt;JAVA-641&lt;/del&gt;&lt;/a&gt;: Updated exception error message for JMX registration to point people to MongoOptions.alwaysUseMBeans property&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo-java-driver/commit/320b82dc497c605bae6328e51c97b11accad0551&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo-java-driver/commit/320b82dc497c605bae6328e51c97b11accad0551&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="234363" author="auto" created="Tue, 8 Jan 2013 19:13:51 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;date&apos;: u&apos;2012-10-21T03:25:18Z&apos;, u&apos;email&apos;: u&apos;jeff.yemin@10gen.com&apos;, u&apos;name&apos;: u&apos;Jeff Yemin&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/JAVA-641&quot; title=&quot;JMX registration error&quot; class=&quot;issue-link&quot; data-issue-key=&quot;JAVA-641&quot;&gt;&lt;del&gt;JAVA-641&lt;/del&gt;&lt;/a&gt;: Added MongoOptions property to control whether driver always uses MBeans.  The default is false, in which case the driver will use MXBeans on Java 6 or greater&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo-java-driver/commit/8d0e70409269be7142d43370bd3fd77af1bb6f41&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo-java-driver/commit/8d0e70409269be7142d43370bd3fd77af1bb6f41&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="234362" author="auto" created="Tue, 8 Jan 2013 19:13:49 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;date&apos;: u&apos;2012-10-19T14:00:09Z&apos;, u&apos;email&apos;: u&apos;jeff.yemin@10gen.com&apos;, u&apos;name&apos;: u&apos;Jeff Yemin&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/JAVA-666&quot; title=&quot;Don&amp;#39;t rely on MXBean&quot; class=&quot;issue-link&quot; data-issue-key=&quot;JAVA-666&quot;&gt;&lt;del&gt;JAVA-666&lt;/del&gt;&lt;/a&gt;, &lt;a href=&quot;https://jira.mongodb.org/browse/JAVA-641&quot; title=&quot;JMX registration error&quot; class=&quot;issue-link&quot; data-issue-key=&quot;JAVA-641&quot;&gt;&lt;del&gt;JAVA-641&lt;/del&gt;&lt;/a&gt;: Created two subclasses of DBPortPool: MongoConnectionPool and Java5MongoConnectionPool.  The former is an MBean and the latter is an MXBean.  When creating a DBPortPool, conditionally create one or the other depending on whether java.version system property indicates that this is a 1.5 virtual machine.  This should avoid JXM registration errors when running on Java 5 VMs. Also, by using MongoConnectionPool as the name of the MXBean, avoids incompatibilities in JMX implementations that require the MXBean name to be the same as the MXBean interface that it implements (minus the MXBean suffix).&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo-java-driver/commit/2ee8c205515c4bec7c166ac1c13ab8c3ba220ac4&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo-java-driver/commit/2ee8c205515c4bec7c166ac1c13ab8c3ba220ac4&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="234347" author="auto" created="Tue, 8 Jan 2013 19:07:17 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;date&apos;: u&apos;2012-10-22T18:29:10Z&apos;, u&apos;email&apos;: u&apos;jeff.yemin@10gen.com&apos;, u&apos;name&apos;: u&apos;Jeff Yemin&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/JAVA-641&quot; title=&quot;JMX registration error&quot; class=&quot;issue-link&quot; data-issue-key=&quot;JAVA-641&quot;&gt;&lt;del&gt;JAVA-641&lt;/del&gt;&lt;/a&gt;: Updated exception error message for JMX registration to point people to MongoOptions.alwaysUseMBeans property&lt;br/&gt;
Branch: 2.10.x&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo-java-driver/commit/320b82dc497c605bae6328e51c97b11accad0551&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo-java-driver/commit/320b82dc497c605bae6328e51c97b11accad0551&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="234346" author="auto" created="Tue, 8 Jan 2013 19:07:15 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;date&apos;: u&apos;2012-10-21T03:25:18Z&apos;, u&apos;email&apos;: u&apos;jeff.yemin@10gen.com&apos;, u&apos;name&apos;: u&apos;Jeff Yemin&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/JAVA-641&quot; title=&quot;JMX registration error&quot; class=&quot;issue-link&quot; data-issue-key=&quot;JAVA-641&quot;&gt;&lt;del&gt;JAVA-641&lt;/del&gt;&lt;/a&gt;: Added MongoOptions property to control whether driver always uses MBeans.  The default is false, in which case the driver will use MXBeans on Java 6 or greater&lt;br/&gt;
Branch: 2.10.x&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo-java-driver/commit/8d0e70409269be7142d43370bd3fd77af1bb6f41&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo-java-driver/commit/8d0e70409269be7142d43370bd3fd77af1bb6f41&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="234345" author="auto" created="Tue, 8 Jan 2013 19:07:14 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;date&apos;: u&apos;2012-10-19T14:00:09Z&apos;, u&apos;email&apos;: u&apos;jeff.yemin@10gen.com&apos;, u&apos;name&apos;: u&apos;Jeff Yemin&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/JAVA-666&quot; title=&quot;Don&amp;#39;t rely on MXBean&quot; class=&quot;issue-link&quot; data-issue-key=&quot;JAVA-666&quot;&gt;&lt;del&gt;JAVA-666&lt;/del&gt;&lt;/a&gt;, &lt;a href=&quot;https://jira.mongodb.org/browse/JAVA-641&quot; title=&quot;JMX registration error&quot; class=&quot;issue-link&quot; data-issue-key=&quot;JAVA-641&quot;&gt;&lt;del&gt;JAVA-641&lt;/del&gt;&lt;/a&gt;: Created two subclasses of DBPortPool: MongoConnectionPool and Java5MongoConnectionPool.  The former is an MBean and the latter is an MXBean.  When creating a DBPortPool, conditionally create one or the other depending on whether java.version system property indicates that this is a 1.5 virtual machine.  This should avoid JXM registration errors when running on Java 5 VMs. Also, by using MongoConnectionPool as the name of the MXBean, avoids incompatibilities in JMX implementations that require the MXBean name to be the same as the MXBean interface that it implements (minus the MXBean suffix).&lt;br/&gt;
Branch: 2.10.x&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo-java-driver/commit/2ee8c205515c4bec7c166ac1c13ab8c3ba220ac4&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo-java-driver/commit/2ee8c205515c4bec7c166ac1c13ab8c3ba220ac4&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="177625" author="auto" created="Mon, 22 Oct 2012 04:50:20 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;date&apos;: u&apos;2012-10-19T07:00:09-07:00&apos;, u&apos;email&apos;: u&apos;jeff.yemin@10gen.com&apos;, u&apos;name&apos;: u&apos;Jeff Yemin&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/JAVA-666&quot; title=&quot;Don&amp;#39;t rely on MXBean&quot; class=&quot;issue-link&quot; data-issue-key=&quot;JAVA-666&quot;&gt;&lt;del&gt;JAVA-666&lt;/del&gt;&lt;/a&gt;, &lt;a href=&quot;https://jira.mongodb.org/browse/JAVA-641&quot; title=&quot;JMX registration error&quot; class=&quot;issue-link&quot; data-issue-key=&quot;JAVA-641&quot;&gt;&lt;del&gt;JAVA-641&lt;/del&gt;&lt;/a&gt;: Created two subclasses of DBPortPool: MongoConnectionPool and Java5MongoConnectionPool.  The former is an MBean and the latter is an MXBean.  When creating a DBPortPool, conditionally create one or the other depending on whether java.version system property indicates that this is a 1.5 virtual machine.  This should avoid JXM registration errors when running on Java 5 VMs. Also, by using MongoConnectionPool as the name of the MXBean, avoids incompatibilities in JMX implementations that require the MXBean name to be the same as the MXBean interface that it implements (minus the MXBean suffix).&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo-java-driver/commit/a215bdf4101033aac08aa72768a4bbe417e83402&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo-java-driver/commit/a215bdf4101033aac08aa72768a4bbe417e83402&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="177545" author="auto" created="Sun, 21 Oct 2012 20:19:55 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;date&apos;: u&apos;2012-10-20T20:25:18-07:00&apos;, u&apos;email&apos;: u&apos;jeff.yemin@10gen.com&apos;, u&apos;name&apos;: u&apos;Jeff Yemin&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/JAVA-641&quot; title=&quot;JMX registration error&quot; class=&quot;issue-link&quot; data-issue-key=&quot;JAVA-641&quot;&gt;&lt;del&gt;JAVA-641&lt;/del&gt;&lt;/a&gt;: Added MongoOptions property to control whether driver always uses MBeans.  The default is false, in which case the driver will use MXBeans on Java 6 or greater&lt;br/&gt;
Branch: release-2.9.x&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo-java-driver/commit/8d0e70409269be7142d43370bd3fd77af1bb6f41&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo-java-driver/commit/8d0e70409269be7142d43370bd3fd77af1bb6f41&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="177488" author="jeff.yemin" created="Sun, 21 Oct 2012 03:20:31 +0000"  >&lt;p&gt;I tested with Jetty 6.1.10, JBoss 4.2.3 AS, and Resin 4.0.32, all under Java 6, using the recently committed code.  None of them work the same.&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;Jetty 6.1.10: MongoConnectionPool MXBean works perfectly&lt;/li&gt;
	&lt;li&gt;JBoss 4.2.3: MongoConnectionPool MXBean doesn&apos;t work: &quot;WARNING: jmx registration error: com.mongodb.util.management.JMException: javax.management.NotCompliantMBeanException: Class does not expose a management interface: java.lang.Object continuing...&quot;&lt;/li&gt;
	&lt;li&gt;Resin 4.0.32: MongoConnectionPool MXBean partially works.  The MXBean register, but the statistics property of type ConnectionPoolStatisticsBean is flagged as unavailable in jconsole.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Since the driver can&apos;t reliably detect the environment it&apos;s running in (except for java version), the only solution is to allow whether MBeans or MXBeans are used to be configured via a property in MongoOptions.  I&apos;m calling it &quot;alwaysUseMBeans&quot;, and it defaults to false.  For JBoss users running Java 6 or later, they should set this property to &quot;true&quot;.  Resin users can use either, but given the problem with the ConnectionPoolStatisticsBean type, &quot;true&quot; might also be a better option.&lt;/p&gt;</comment>
                            <comment id="177472" author="auto" created="Sat, 20 Oct 2012 23:32:58 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;date&apos;: u&apos;2012-10-19T07:00:09-07:00&apos;, u&apos;email&apos;: u&apos;jeff.yemin@10gen.com&apos;, u&apos;name&apos;: u&apos;Jeff Yemin&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/JAVA-666&quot; title=&quot;Don&amp;#39;t rely on MXBean&quot; class=&quot;issue-link&quot; data-issue-key=&quot;JAVA-666&quot;&gt;&lt;del&gt;JAVA-666&lt;/del&gt;&lt;/a&gt;, &lt;a href=&quot;https://jira.mongodb.org/browse/JAVA-641&quot; title=&quot;JMX registration error&quot; class=&quot;issue-link&quot; data-issue-key=&quot;JAVA-641&quot;&gt;&lt;del&gt;JAVA-641&lt;/del&gt;&lt;/a&gt;: Created two subclasses of DBPortPool: MongoConnectionPool and Java5MongoConnectionPool.  The former is an MBean and the latter is an MXBean.  When creating a DBPortPool, conditionally create one or the other depending on whether java.version system property indicates that this is a 1.5 virtual machine.  This should avoid JXM registration errors when running on Java 5 VMs. Also, by using MongoConnectionPool as the name of the MXBean, avoids incompatibilities in JMX implementations that require the MXBean name to be the same as the MXBean interface that it implements (minus the MXBean suffix).&lt;br/&gt;
Branch: release-2.9.x&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo-java-driver/commit/2ee8c205515c4bec7c166ac1c13ab8c3ba220ac4&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo-java-driver/commit/2ee8c205515c4bec7c166ac1c13ab8c3ba220ac4&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="175447" author="jeff.yemin" created="Tue, 16 Oct 2012 15:05:57 +0000"  >&lt;p&gt;We&apos;re going to look to roll back this change.  See &lt;a href=&quot;https://jira.mongodb.org/browse/JAVA-666&quot; title=&quot;Don&amp;#39;t rely on MXBean&quot; class=&quot;issue-link&quot; data-issue-key=&quot;JAVA-666&quot;&gt;&lt;del&gt;JAVA-666&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="175439" author="cohenma" created="Tue, 16 Oct 2012 14:59:10 +0000"  >&lt;p&gt;Jeff, we see the same issue with JBoss 4.2.3, FYI.  We&apos;ll see if this is something that JBoss has taken care of in a later version.  Would it make sense to start testing with more than just the Sun JMX provider to catch these kinds of issues?&lt;/p&gt;

&lt;p&gt;thx&lt;/p&gt;</comment>
                            <comment id="175430" author="jeff.yemin" created="Tue, 16 Oct 2012 14:49:16 +0000"  >&lt;p&gt;Raman, it&apos;s just monitoring.&lt;/p&gt;</comment>
                            <comment id="175401" author="raman_yushkou@epam.com" created="Tue, 16 Oct 2012 13:57:10 +0000"  >&lt;p&gt;How this issue affects driver behavior (does it critically influence on driver work or it&apos;s just a monitoring)?&lt;/p&gt;</comment>
                            <comment id="164153" author="jeff.yemin" created="Thu, 13 Sep 2012 19:55:32 +0000"  >&lt;p&gt;Seems like an issue with CAPTCHA.  I keep getting &quot;Confirmation hash does not match. Please retry.&quot;.&lt;/p&gt;</comment>
                            <comment id="163913" author="kay.agahd@idealo.de" created="Thu, 13 Sep 2012 13:29:01 +0000"  >&lt;p&gt;You couldn&apos;t sign up for a new account? It worked for me just some hours ago. Could you try again?&lt;/p&gt;</comment>
                            <comment id="163907" author="jeff.yemin" created="Thu, 13 Sep 2012 13:23:52 +0000"  >&lt;p&gt;OK, thanks.  Let me know what their response is.  Resin&apos;s Mantis bug tracking system is not letting me sign up for a new account. &lt;/p&gt;</comment>
                            <comment id="163889" author="kay.agahd@idealo.de" created="Thu, 13 Sep 2012 12:25:51 +0000"  >&lt;p&gt;Yes, I just submitted a bug report:&lt;br/&gt;
&lt;a href=&quot;http://bugs.caucho.com/view.php?id=5212&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://bugs.caucho.com/view.php?id=5212&lt;/a&gt; &lt;/p&gt;</comment>
                            <comment id="163876" author="jeff.yemin" created="Thu, 13 Sep 2012 11:57:19 +0000"  >&lt;p&gt;I&apos;d rather fix Resin, since the bug is theirs and it&apos;s going to cause problems for other JMX clients.  Have you tried their support forums?&lt;/p&gt;</comment>
                            <comment id="163839" author="kay.agahd@idealo.de" created="Thu, 13 Sep 2012 09:37:45 +0000"  >&lt;p&gt;You are right, other application servers, as for example Glassfish too, don&apos;t throw any jmx registration errors.&lt;br/&gt;
However, Resin does and I&apos;m wondering whether it&apos;s better to fix resin or the mongo driver.&lt;br/&gt;
What do you think?&lt;/p&gt;</comment>
                            <comment id="163689" author="jeff.yemin" created="Wed, 12 Sep 2012 21:53:57 +0000"  >&lt;p&gt;According to &lt;a href=&quot;http://docs.oracle.com/javase/6/docs/api/javax/management/MXBean.html:&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://docs.oracle.com/javase/6/docs/api/javax/management/MXBean.html:&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;ul&gt;
	&lt;li&gt;Otherwise, it may be an MXBean. The set of interfaces implemented by the object is examined for interfaces that:
	&lt;ul&gt;
		&lt;li&gt;have a class name SMXBean where S is any non-empty string, and do not have an annotation @MXBean(false); and/or&lt;/li&gt;
		&lt;li&gt;have an annotation @MXBean(true) or just @MXBean.&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;

&lt;p&gt;And I don&apos;t see any problems registering this MXBean with Sun&apos;s JMX provider.  So this may be a problem with the JMX provider used in Resin.&lt;/p&gt;</comment>
                            <comment id="163507" author="kay.agahd@idealo.de" created="Wed, 12 Sep 2012 16:18:23 +0000"  >&lt;p&gt;The same applies to v2.9.1&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Depends</name>
                                            <outwardlinks description="depends on">
                                        <issuelink>
            <issuekey id="61334">JAVA-724</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="53044">JAVA-666</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hrhm9b:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>16415</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            </customfields>
    </item>
</channel>
</rss>