<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 08:52:48 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-666] Don&apos;t rely on MXBean</title>
                <link>https://jira.mongodb.org/browse/JAVA-666</link>
                <project id="10006" key="JAVA">Java Driver</project>
                    <description>&lt;p&gt;The driver recently switched to using MXBean, which doesn&apos;t work on Java 5.  This was unintentional and should be reverted.&lt;/p&gt;</description>
                <environment></environment>
        <key id="53044">JAVA-666</key>
            <summary>Don&apos;t rely on MXBean</summary>
                <type id="4" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14710&amp;avatarType=issuetype">Improvement</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="jeff.yemin@mongodb.com">Jeffrey Yemin</reporter>
                        <labels>
                    </labels>
                <created>Fri, 12 Oct 2012 19:11:15 +0000</created>
                <updated>Tue, 8 Jan 2013 19:13:48 +0000</updated>
                            <resolved>Mon, 22 Oct 2012 04:51:48 +0000</resolved>
                                    <version>2.9.0</version>
                                    <fixVersion>2.9.2</fixVersion>
                    <fixVersion>2.10.0</fixVersion>
                                    <component>API</component>
                    <component>Monitoring</component>
                                        <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="234361" author="auto" created="Tue, 8 Jan 2013 19:13:48 +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="234344" author="auto" created="Tue, 8 Jan 2013 19:07:13 +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="177624" author="auto" created="Mon, 22 Oct 2012 04:50:19 +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="177471" author="auto" created="Sat, 20 Oct 2012 23:32:57 +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="177399" author="jeff.yemin" created="Sat, 20 Oct 2012 01:15:29 +0000"  >&lt;p&gt;I have a fix for this that I think will work:  DBPortPool will no longer be either an MBean or an MXBean.  Instead, there will be two subclasses of DBPortPool: MongoConnectionPool and Java5MongoConnectionPool.  The former will be an MXBean and the latter an MBean.  At run-time, the driver will detect the Java version (java.version system property) and instantiate a Java5MongoConnectionPool if it&apos;s 1.5 and MongoConnectionPool otherwise.  I&apos;ll also make sure that the MBean/MXBean interfaces have names that match the classes that implement them: MongoConnectionPoolMXBean and Java5MongoConnectionPoolMBean, respectively.  This should take care of the Resin/JBoss issues reported on &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;.&lt;/p&gt;</comment>
                            <comment id="175560" author="cohenma" created="Tue, 16 Oct 2012 17:53:17 +0000"  >&lt;p&gt;We&apos;re having the problem from &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; using JDK 1.6.0_21 as an FYI.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Depends</name>
                                                                <inwardlinks description="is depended on by">
                                                        </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                        <issuelink>
            <issuekey id="50341">JAVA-641</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </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|hrjyv3:</customfieldvalue>

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