<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Wed Feb 07 21:37:07 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>[CSHARP-534] MongoServerInstance.AcquireConnection throws InvalidOperationException</title>
                <link>https://jira.mongodb.org/browse/CSHARP-534</link>
                <project id="10041" key="CSHARP">C# Driver</project>
                    <description>&lt;p&gt;When server instance gets disconnected and state verification have not yet kicked in, MongoServerInstance.AcquireConnection throws InvalidOperationException(&quot;Server instance XXX is no longer connected.&quot;). While this is an internal state problem (so IOE fits the scheme), I think it should be treated as a transient connection error and instead throw a MongoConnectionException (with the same message). For us, the exception types are really important, because we&apos;ve built an auto-retry mechanism around driver calls, and catching something as ambiguous as InvalidOperationException makes robust error handling hard enough.&lt;/p&gt;</description>
                <environment></environment>
        <key id="45153">CSHARP-534</key>
            <summary>MongoServerInstance.AcquireConnection throws InvalidOperationException</summary>
                <type id="1" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14703&amp;avatarType=issuetype">Bug</type>
                                            <priority id="4" iconUrl="https://jira.mongodb.org/images/icons/priorities/minor.svg">Minor - P4</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="-1">Unassigned</assignee>
                                    <reporter username="onyxmaster">Aristarkh Zagorodnikov</reporter>
                        <labels>
                            <label>exception</label>
                    </labels>
                <created>Mon, 23 Jul 2012 20:56:43 +0000</created>
                <updated>Thu, 20 Mar 2014 14:34:54 +0000</updated>
                            <resolved>Mon, 12 Nov 2012 21:36:41 +0000</resolved>
                                    <version>1.5</version>
                                                                        <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="187032" author="craiggwilson" created="Mon, 12 Nov 2012 21:36:41 +0000"  >&lt;p&gt;Sounds good.  Thanks...&lt;/p&gt;</comment>
                            <comment id="187017" author="onyxmaster" created="Mon, 12 Nov 2012 21:27:54 +0000"  >&lt;p&gt;Since the linked issue completely encompasses this case, I think this issue can be closed as &lt;a href=&quot;https://jira.mongodb.org/browse/CSHARP-153&quot; title=&quot;Wrapping internal communication exceptions&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CSHARP-153&quot;&gt;&lt;del&gt;CSHARP-153&lt;/del&gt;&lt;/a&gt; was.&lt;/p&gt;</comment>
                            <comment id="186625" author="craiggwilson" created="Mon, 12 Nov 2012 16:03:48 +0000"  >&lt;p&gt;We have a ticket for reviewing all the exceptions thrown by the driver and, in most cases, will be wrapping them in a MongoXXXException.  I&apos;m going to link this ticket to that one in order to make sure this one gets covered.&lt;/p&gt;</comment>
                            <comment id="146478" author="onyxmaster" created="Tue, 24 Jul 2012 08:10:42 +0000"  >&lt;p&gt;System.InvalidOperationException: Server instance fs.drive.bru:27017 is no longer connected.&lt;br/&gt;
   at MongoDB.Driver.MongoServerInstance.AcquireConnection(MongoDatabase database) in C:\Users\onyXMaster\Projects\bru\dependencies-source\MongoDB\mongo-csharp-driver\git\Driver\Core\MongoServerInstance.cs:line 288&lt;br/&gt;
   at MongoDB.Driver.MongoServer.RequestStart(MongoDatabase initialDatabase, Boolean slaveOk) in C:\Users\onyXMaster\Projects\bru\dependencies-source\MongoDB\mongo-csharp-driver\git\Driver\Core\MongoServer.cs:line 1062&lt;br/&gt;
   at MongoDB.Driver.GridFS.MongoGridFS.Upload(Stream stream, String remoteFileName, MongoGridFSCreateOptions createOptions) in C:\Users\onyXMaster\Projects\bru\dependencies-source\MongoDB\mongo-csharp-driver\git\Driver\GridFS\MongoGridFS.cs:line 780&lt;br/&gt;
...&lt;/p&gt;

&lt;p&gt;Line numbers are from our patched 1.4 version, so take them with a grain of salt =)&lt;/p&gt;</comment>
                            <comment id="146469" author="onyxmaster" created="Tue, 24 Jul 2012 07:39:50 +0000"  >&lt;p&gt;I work against the 1.4 version, but testing with master shows the same behavior. This occurs when we use the GridFS API that in it&apos;s turn uses the RequestStart wrapper to ensure that all same-file requests go to the same server. I guess that all code using RequestStart would be susceptible to this issue.&lt;/p&gt;</comment>
                            <comment id="146449" author="craiggwilson" created="Tue, 24 Jul 2012 05:38:49 +0000"  >&lt;p&gt;1) Are you working against the published 1.5 driver or have you built from master?&lt;br/&gt;
2) It seems like the type of error you are describing would happen in the background...  where are you catching these exceptions?  Perhaps you could provide some sample code of where this exception shows up in user code.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="39411">CSHARP-474</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                        <customfield id="customfield_10011" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Backwards Compatibility</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10011"><![CDATA[Minor Change]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <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|hrh79b:</customfieldvalue>

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